Fedora 13, I mean Jesse, and I were just talking on IRC about the
scheduling of the final "Go/No-Go" meeting. This is the meeting where
all the key engineering teams meet to declare the release GOLD or not.
In the past it has been Jesse's understanding that certain teams need
decent lead time to "stop the presses" if our scheduled release date
will NOT be met.
For Fedora 13 we have the "Go/No-Go" meeting scheduled for 2010-04-19 (8
days before the public release on 2010-04-27) with the content going to
the mirrors on 2010-04-22.
If we were to move the "Go/No-Go" meeting closer to 2010-04-22 by a day
or two (say TUES 2010-04-21 or WED 2010-04-20) would that cause problems
for any of the teams if we were to declare on one of those dates that we
were NOT releasing on the originally scheduled date?
Please reply ASAP as we are trying to finalize the Fedora 13 dates soon.
Apparently over the past week Zikula 1.2.0 was released, and includes,
among other things some modifications for modules using gettext for
internationalization (I believe core Zikula stuff was already using
gettext, but modules weren't)
I have just started looking at this, but wanted to give a heads up, it
will likely be a few weeks before I check a package in, as I have
already seen at least one or two new bundled libraries that I don't
believe are in Fedora yet.
Fedora 12 is a "GO" and testing continues in anticipating of staging the
final content to the mirrors on 2009-11-12.
When: 2009-11-11 at 20:00 UTC (3 PM EST/12 PM PST)
Where: IRC #fedora-meeting on freenode
This Wednesday we will have the Release Readiness meeting for the Fedora
12 Final release to coordinate and discuss release day issues in real
time and to make sure we are ready for a smooth release day. Please
make sure someone from your team is able to attend.
The following list shows the people that represented these teams in past
releases. If you cannot attend or no longer wish to represent your team
please coordinate an alternate.
Ambassadors -- David Nalley
Design -- Máirín Duffy
Documentation -- Eric Christensen
FESCo -- Jon Stanley
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Paul Frields
Infrastructure -- Mike McGrath
Marketing -- Mel Chua
Quality -- James Laska
Release Engineering -- Jesse Keating
Translation -- Noriko Mizumoto
Websites -- Ricky Zhou
Testing of the latest Fedora 12 release candidate (RC4) is underway and
a meeting will be held on #fedora-meeting today at 20:00 EST TODAY
(01:00 AM UTC Tues)to determine if there are any known blocker bugs
which would cast doubt on our ability to release on our current GA date
of record: 2009-11-17.
After the "Go/No Go" meeting I will also announce the final release
readiness meeting... either this coming Wednesday or the following
Wednesday @ 19:00 UTC (3 PM EDT/12 PM PDT).
In the meantime help test if you can.
I'm in #fedora-mktg and #fedora-admin (mostly logging in the former,
working on deployment in the latter) from now 'till about 4 hours from
now (or so) trying to clean up the remaining FI work we've got.
At that point, I'm going to need to put down FI work for a while, since
I'm going to be out in Singapore for
http://teachingopensource.org/index.php/POSSE_APAC for most of the rest
of the release cycle. I'm hoping to leave tonight with a clear log of
what's been done and what is left to do.
In general, most of this week will be me trying to loudly and clearly
articulate what's left to be done as far as F12 deliverables go - what's
going to happen, what still needs to be picked up, and who we should be
profusely thanking. For instance, Robyn and Paul have both finished
their F12 Feature Profiles (yay!), leaving the third (mine) to be edited
- but we have no screenshots, so if someone could step up and organize a
sprint, that would be great).
This will be the overriding theme of the week, particularly tomorrow's
meeting. :) But right now, I'm working on FI.