<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.0">
</HEAD>
<BODY>
On Tue, 2006-12-12 at 17:37 -0500, Max Spevack wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Tue, 12 Dec 2006, Thorsten Leemhuis wrote:</FONT>
<FONT COLOR="#000000">> January 02 is probably to hard to reach, so we should cut one cycle from </FONT>
<FONT COLOR="#000000">> four to three weeks. Which one? test3 maybe?</FONT>
<FONT COLOR="#000000">We talked about this in the Board meeting this morning.</FONT>
<FONT COLOR="#000000">Here was the proposal we came up with (modified for a Tuesday release, not </FONT>
<FONT COLOR="#000000">a Monday release), working backward:</FONT>
<FONT COLOR="#000000">RH Summit May 9-11</FONT>
<FONT COLOR="#000000">Release April 24 (exactly 6 months after FC6)</FONT>
<FONT COLOR="#000000">Gold April 17</FONT>
<FONT COLOR="#000000">Test3 March 27</FONT>
<FONT COLOR="#000000">Test2 February 27</FONT>
<FONT COLOR="#000000">FudCon February 9-11 (including hackfest)</FONT>
<FONT COLOR="#000000">Test1 January 30</FONT>
<FONT COLOR="#000000">Not a lot of slip time in there (at least, not with the RH Summit as a </FONT>
<FONT COLOR="#000000">target).</FONT>
</PRE>
</BLOCKQUOTE>
The reverse-chronological list above defines some dates for releases of things that might be called "deliverables". These deliverables are currently all software trees.<BR>
<BR>
Is it possible to add the high-level objectives for what a release might contain as the first deliverable?<BR>
- integrate Core and Extras<BR>
- orbital laser integrated into GUI control system<BR>
- integrate lobby-buddy [1] throughout the distro <BR>
- reduce the bootup time<BR>
- attempt to fix system services<BR>
- enhanced, integrated bling for the desktop<BR>
- static analysis for the whole distro<BR>
or whatever... (currently the only thing I know of for F7 is the first one)<BR>
<BR>
We'd then put time in at the top of the schedule to try to define these high-level themes for F7.<BR>
<BR>
So the list of deliverables (in forward chronological order) might look like this:<BR>
- Jan 1st: roadmap for release (features, high-priority bugs, fallback plans in case things aren't going to land in time) <BR>
- [ Period of time where development happens, testers try to figure out how to test things, and rawhide eats people's branes ]<BR>
- <FONT COLOR="#000000">January 30</FONT>: Test1<BR>
- <FONT COLOR="#000000">February 27</FONT>: Test2<BR>
- <FONT COLOR="#000000">April 17</FONT>: Gold<BR>
- <FONT COLOR="#000000">April 24</FONT>: Release<BR>
- party<BR>
- May 7th: post-mortem report (feeding into the roadmap for the next release)<BR>
<BR>
IMHO the only way we can get whole-distribution improvements rather than incremental changes here and there is to try to define and aim for them at the start of a development cycle.<BR>
<BR>
Thoughts?<BR>
Dave<BR>
<BR>
[1] <A HREF="https://www.redhat.com/archives/fedora-devel-list/2006-December/msg00032.html">https://www.redhat.com/archives/fedora-devel-list/2006-December/msg00032.html</A>
</BODY>
</HTML>