I have setup some machines/virtual instances here to assist maintainers
that might not have access to all versions/arches Fedora runs on.
For more information on the instances, how to use them and common
questions and answers.
Feel free to email me with any outstanding questions you might have
about the instances, and I hope they are useful.
One thing we overlooked by dropping the Alpha Release (as we knew it in
Fedora 11 and before) is the built-in feature check at Alpha freeze. As
a result we need all feature owners to update their feature pages with
current completion information by July 14, 2009.
I'll be forwarding a list of stale feature pages (hopefully there won't
be any) to FESCo for their review on July 17, 2009.
This checkpoint is important to know if currently accepted features are
on track for a successful Fedora 12 landing or if contingency plans need
to be considered at Feature Freeze as we prepare for the Alpha release.
Tracking important development dates has never been easier!
(Import to Zimbra, Google Calendar, etc.)
Thanks for your help,
The logistics(a)lists.fedoraproject.org mailing list has been created to
meet the requirements discussed here:
Anyone is welcome to join the list at:
participants are strongly encouraged to use it only for important topics
that need to be coordinated across teams.
I have also take the liberty to sign up leads from each the teams that
attended the Fedora 11 Release Readiness meetings (assuming they will be
the same for Fedora 12) as well as the people who have expressed an
interest in helping with or learning more about the Fedora Zikula CMS
implementation. Feel free to adjust things by adding or removing yourself.
We in the QA and BugZappers groups have been working for a while on a
proposal to use the severity and priority fields in Bugzilla. With the
help of various groups, and after considerable feedback both within our
groups and from the development group, we're ready to put this into
To briefly explain the system, the priority field will be reserved by
policy for developers only. You can use it to organize bugs into the
order you'd like to tackle them. Or, you can not. It's entirely up to
you. The policy makes maintainers the sole 'owners' of this field;
no-one else is supposed to touch it, and there are no rules or
guidelines for how it should be used, it's entirely up to developers'
discretion. Significantly, Bugzilla is now configured so that only
members of the 'fedorabugs' FAS group can touch this field, so there is
less chance that - if you decide to actually use it - disgruntled
users / reporters will mess with your settings.
The severity field is reserved by policy to the Bugzappers team and
developers. Again, it's been restricted in Bugzilla now so that only
members of 'fedorabugs' can touch it. The policy is that triagers will
set this field initially as part of triage, but developers have the
final say, and if a developer decides to change the setting chosen by a
triager, the triager is to accept that decision and not change it back.
The guidelines for how the various settings should be used are here:
The severity setting will be used in future as part of the QA and
BugZapper processes - for instance, we're planning to do a weekly review
of 'urgent' severity bugs, and will also review these during blocker bug
This policy and the changes to Bugzilla configuration are all in line
with proposals made during the last few weeks, and sent for feedback to
-devel-list a few weeks back. No opposition has been received to the
proposal in this form. Having said that, if you have a big problem with
this policy, please do let us know and we'll try to accommodate your
Thanks very much, and please do contact me directly or test-list (or
anyone else in QA or BugZappers) with any questions relating to this.
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
Please see below from our fabulous releng team!
---------- Forwarded message ----------
From: Josh Boyer <jwboyer(a)gmail.com>
Date: Tue, Jun 30, 2009 at 6:24 PM
Subject: Last call for F9 updates
F9 will be EOL'd very very soon. This is probably the last call for updates
I wouldn't bother with updates-testing, as the time required to properly get
those pushed out and have feedback from them is longer than the EOL date. That
does not mean to push untested stuff straight to stable.
fedora-devel-list mailing list