Ticket #5215 (new task)
Opened 21 months ago
Stage comps and spin-kickstarts during freezes
|Reported by:||adamwill||Owned by:||rel-eng@…|
|Milestone:||Fedora 18 Alpha||Component:||git|
As noted on the F17 QA retrospective by me and Bruno Wolff:
it's a problem that we use git master of both comps and spin-kickstarts for composes - not the latest packaged version - and both these git repos are not frozen during freezes.
During the 17 cycle, we had a concrete example of a comps change during a freeze causing considerable trouble: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=807879 - pulling Boxes into comps during the Beta freeze made that issue a serious problem. For spin-kickstarts, the same kind of thing is possible, and we also have a release criterion requiring a spin-kickstarts package which matches the .ks files used for the compose to be present in the release repository; obviously, the lack of a git freeze makes this tricky to ensure.
So we would strongly recommend, at minimum, a mechanism for freezing spin-kickstarts and comps at Alpha, Beta and Final freeze. Post-freeze changes could be made following the same blocker/NTH process used for other post-freeze changes.