Clarify Noble activation in cf-deployment

beyhan · beyhan · commit 2e4bd6d4d0d0 · 2024-03-15T11:56:02.000+01:00
diff --git a/toc/rfc/rfc-draft-noble-os.md b/toc/rfc/rfc-draft-noble-os.md
@@ -44,4 +44,4 @@ The end of planned support for Jammy Jellyfish (22.04) is 06.2027. That is why f
 
 ### App Runtime Deployments WG
 
-Once initial confidence has been gained by validating the Noble Numbat stemcell against the BOSH director it is time to validate against cf-deployment. A simular validation like the one existing for Jammy stemcell should be set up for Noble which will use the beta 0.x version of the stemcell provided by the FI WG. GCP will be used as the initial validation environment but if required validation on AWS could be added. Issues discovered by this validation should be distributed to the related CF components. It is their responsibility to address them. If CF components want to have faster feedback on Noble Numbat issues they can add their own validation. When the cf-deployment validation of Noble is successful the FI WG will release the 1.x GA version of the Noble Numbat stemcell. The Noble Numbat validation in cf-deployment will be kept also after the 1.x GA release.
+Once initial confidence has been gained by validating the Noble Numbat stemcell against the BOSH director it is time to validate against cf-deployment. A simular validation like the one existing for Jammy stemcell should be set up for Noble which will use the beta 0.x version of the stemcell provided by the FI WG. GCP will be used as the initial validation environment but if required validation on AWS could be added. Issues discovered by this validation should be distributed to the related CF components. It is their responsibility to address them. If CF components want to have faster feedback on Noble Numbat issues they can add their own validation. When the cf-deployment validation of Noble is successful the FI WG will release the 1.x GA version of the Noble Numbat stemcell. The Noble Numbat validation in cf-deployment will be kept also after the 1.x GA release. At this point cf-deployment will also provide an `ops-file`, which can be used by CF operators to switch to Noble Numbat. Additionally, cf-deployment should decide to make the Noble stemcell the default one well before the EOF for Jammy so that CF operators have enough time to migration from Jammy to Noble.

Original file line number	Diff line number	Diff line change
`@@ -44,4 +44,4 @@ The end of planned support for Jammy Jellyfish (22.04) is 06.2027. That is why f`
`44`	`44`
`45`	`45`	`### App Runtime Deployments WG`
`46`	`46`
`47`		-Once initial confidence has been gained by validating the Noble Numbat stemcell against the BOSH director it is time to validate against cf-deployment. A simular validation like the one existing for Jammy stemcell should be set up for Noble which will use the beta 0.x version of the stemcell provided by the FI WG. GCP will be used as the initial validation environment but if required validation on AWS could be added. Issues discovered by this validation should be distributed to the related CF components. It is their responsibility to address them. If CF components want to have faster feedback on Noble Numbat issues they can add their own validation. When the cf-deployment validation of Noble is successful the FI WG will release the 1.x GA version of the Noble Numbat stemcell. The Noble Numbat validation in cf-deployment will be kept also after the 1.x GA release.
	`47`	+Once initial confidence has been gained by validating the Noble Numbat stemcell against the BOSH director it is time to validate against cf-deployment. A simular validation like the one existing for Jammy stemcell should be set up for Noble which will use the beta 0.x version of the stemcell provided by the FI WG. GCP will be used as the initial validation environment but if required validation on AWS could be added. Issues discovered by this validation should be distributed to the related CF components. It is their responsibility to address them. If CF components want to have faster feedback on Noble Numbat issues they can add their own validation. When the cf-deployment validation of Noble is successful the FI WG will release the 1.x GA version of the Noble Numbat stemcell. The Noble Numbat validation in cf-deployment will be kept also after the 1.x GA release. At this point cf-deployment will also provide an `ops-file`, which can be used by CF operators to switch to Noble Numbat. Additionally, cf-deployment should decide to make the Noble stemcell the default one well before the EOF for Jammy so that CF operators have enough time to migration from Jammy to Noble.