Bug 2096419

Summary:	Return Cloud Base to Edition Status
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	Changes Tracking	Assignee:	David Duncan <davdunc>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	bcotton, davdunc, ngompa13
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 16:25:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2016049

Description Ben Cotton 2022-06-13 18:53:26 UTC

This is a tracking bug for Change: Return Cloud Base to Edition Status
For more details, see: https://fedoraproject.org/wiki/Changes/RestoreCloudEdition

Cloud should be listed on getfedora.org with Workstation, Server and IoT. The petition to reinstate the Cloud Base as an official Edition is based on the clear identification of unique environmental support requirements for private hyperscaler and public cloud environments not specifically addressed by other Editions.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Ben Cotton 2022-08-09 16:02:52 UTC

Today we reached the Code Complete (Testable) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F38, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 2 Ben Cotton 2022-08-23 19:20:29 UTC

Today we reached the Code Complete (100% complete) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be 100% complete. You can indicate this by setting this tracker to the ON_QA status. If you need to defer this Change to F38 please NEEDINFO me.

Note that we are entering the Beta freeze. Additional package changes to complete this Change will need an approved blocker or freeze exception. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for more information.

Changes that have not reached the ON_QA status will be given to FESCo for evaluation of contingency plans.

Comment 3 David Duncan 2022-09-29 14:41:07 UTC

Looks like we need a FESCo review for contingency. Nothing has been missing since 8-23. I just missed the bug. 
@ngompa13 Can you help me get this in front of the council?

Comment 4 Ben Cotton 2022-09-29 14:46:28 UTC

If you're on track for getting everything lined up (particularly the website) for F37 GA, then there's nothing that needs to go to FESCo or Council at this point.

Comment 5 Neal Gompa 2022-09-30 10:34:26 UTC

(In reply to Ben Cotton from comment #4)
> If you're on track for getting everything lined up (particularly the
> website) for F37 GA, then there's nothing that needs to go to FESCo or
> Council at this point.

I suspect the website is the problem here. With the beta we didn't get on getfedora.org, and I don't know what the state of that transition is.

Comment 6 Ben Cotton 2022-11-15 16:25:03 UTC

F37 was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP.