For anyone who has not (yet) read this on the -devel or -devel-announce mailing list, here's how this is going to end:
Features (in our case, spins) which are not approved by FESCo Aug 19th, will -no matter how regrettable- not make it into the release.
Even if in your perception is your spin is approved by the Spin SIG, approved by the Board to carry the Fedora trademark, and approved by FESCo, now is the time to poke around and shake up some people to verify if that's really the case, or you're in for a big disappointment.
The following spins carry the Spin SIG approved flag:
fedora-livecd-desktop-default.ks fedora-livecd-education-math.ks fedora-livecd-kde.ks fedora-livecd-xfce.ks fedora-livedvd-developer.ks fedora-livedvd-electronic-lab.ks fedora-livedvd-games.ks
Awaiting approval is:
fedora-livecd-broffice.org.ks
And they will be put through compose tests over the next week. You will need to ensure your kickstart composes nice and easy, using the latest livecd-tools in rawhide, against the rawhide trees, note bug numbers related to your spin in the kickstart, and sign-off on them becoming a feature to be released by the Fedora Project, with help of the Fedora Project, before the Big Evil Beta Freeze, so that FESCo can verify and Release Engineering can compose.
Note that this endeavor also requires your Feature page on the wiki to be in the appropriate category (CategoryProposedFeaturesF10 IIRC, please check for yourselves), so that FESCo has a tracker.
Kind regards,
Jeroen van Meeuwen -kanarip
-------- Original Message -------- Subject: Fedora 10 Beta Freeze coming soon Date: Mon, 11 Aug 2008 13:02:55 -0400 From: Jesse Keating jkeating@redhat.com Reply-To: fedora-devel-list@redhat.com Organization: Red Hat To: fedora-devel-announce@redhat.com
The Fedora 10 Beta freeze is scheduled for the 19th of Aug, one week and one day away. I know it hasn't been very long since the Alpha release, but that's how we roll here in the land of 6 month release cycles.
Beta freeze also marks the Feature freeze, so it is very important that you get your features into working, testable shape by then, or be prepared to try your feature again for Fedora 11.
We'd like to treat rawhide as a slushy freeze at this point, we'll be doing full composes against rawhide to test for various things and be ahead of the curve come actual freeze time, so we'd like you to not land any really dangerous changes without extensive testing first, and notification to the Fedora lists about your scary change. If we all work together we can get through the beta freeze period quickly and be on to the bugfixing mode after beta releases.
http://fedoraproject.org/wiki/Releases/10/Schedule is the current schedule, although releng/Fesco/Board has the ability to change the schedule as needed. This week's meetings of the various boards, sigs, groups, etc.. should focus on Beta readiness. It would be good to take a moment to see what state your area of interest is in, and how likely it would be that said area of interest will be in a "testable" shape by the Beta freeze. If more (reasonable) time is needed, now is the time to let the project know so that we can effectively manage the remainder of our release schedule.
Thanks for all your hard work in making Fedora 10 great!