Learn more about these different git repos.
Other Git URLs
Need to finalize Fedora 13 schedule and forward on to FESCo soon. We have dependencies with NFR and it would be to our benefit to have a solid schedule going into FUDCon so if possible I would like us to ratify at our meeting on 2009-11-23.
highlights from: http://lists.fedoraproject.org/pipermail/rel-eng/2009-November/008884.html
Which scenario is preferred? * http://poelstra.fedorapeople.org/schedules/f-13-draft/fedora-13-scenario1.pdf * http://poelstra.fedorapeople.org/schedules/f-13-draft/fedora-13-scenario2.pdf
More data and other formats : http://poelstra.fedorapeople.org/schedules/f-13-draft/
Through a long IRC conversation with Bill Nottingham, John Poelstra, Jesse Keating, and Dennis Gilmore, we've greenlit scenario #1 but with a few conditionals.
A) QA signs off as well. B) We don't conflict with any major Linux distro release and cause mirrors to hate us C) We find a happy place for go / nogo events for Alpha/Beta
With respect to point C, jlaska, can you attend next week's rel-eng IRC meeting and we can nail that down? (Or, if you've got a better suggestion for time & place, let us know.)
Updated the wiki to reflect the scenario under discussion: * https://fedoraproject.org/wiki/Releases/13/Schedule
Replying to [comment:2 jkeating]:
Through a long IRC conversation with Bill Nottingham, John Poelstra, Jesse Keating, and Dennis Gilmore, we've greenlit scenario #1 but with a few conditionals. A) QA signs off as well.
A) QA signs off as well.
While both proposed changes meet my hope of having the same test tasks for each major milestone (Alpha, Beta, GA) ... I'm happy with the scenario#1. Scenario#1 also opens up a bit more room for beta feedback which I don't think is a bad thing.
B) We don't conflict with any major Linux distro release and cause mirrors to hate us C) We find a happy place for go / nogo events for Alpha/Beta
I like the idea of moving the go/nogo event to the Wednesday, and the content sync starts on Thursday. The IRC thread also points out a need to clarify the goal of the go/nogo meeting ... I think we'd all benefit from adding some context around the meeting.
I'll need to work back with the team to make sure our testing tasks are completed in time for the meeting.
Executive Summary: We are blocked on setting a final date until we have more information from the mirrors.
Jesse and I have talked a little more on #fedora-devel and researched a few other things. Here is a current status:
RE: Items 1-4 above. 2-4 have been resolved with today's meeting where the decision was made to add two weeks to the Fedora 13 schedule.
Item 1 is still open, hoping to get feedback from Paul Frields when he returns.
I've created a ticket with FESCo to review and approve the Fedora 13 schedule. https://fedorahosted.org/fesco/ticket/281
In the associated FESCo ticket Kevin Kofler asks what a shorter schedule by two weeks would look like.
My response:
http://poelstra.fedorapeople.org/schedules/f-13-draft/f-13-two-weeks- early.html
This would be less favorable considering where feature freeze lands and how soon the Alpha would be. It might also possibly be the shortest release in Fedora's history.
This was done I do believe. Please re-open if not.
Metadata Update from @poelstra: - Issue tagged with: meeting
Login to comment on this ticket.