I actually like your schedule better - I've been corrected on my definition of RCs and do agree that more betas is better than more RCs.<br><br><div><span class="gmail_quote">On 27/08/07, <b class="gmail_sendername">Allen Winter
</b> <<a href="mailto:winter@kde.org">winter@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Monday 27 August 2007 6:54:47 pm Troy Unrau wrote:
<br><br>> 1) We add another beta into the release cycle pushing the release<br>> candidates back. This ensures that we actually have a beta with the<br>> plasma panel and not kicker.<br><br>Extra time doesn't ensure anything.
<br>But, I'm fine with adding another beta.<br>The Milestones[1] say that we "estimated" 2 betas.<br>The Release Schedule[2] says that "dates are subject to change".<br><br>> 2) We add an additional two RC's (for a total of 4 RCs) to ensure that
<br>> the code works, and isn't a festering dung-heap when we release it.<br><br>[1] says that the Release Candidate Cycle continues until we fix<br>all grave bugs. It also says that we "estimated" 2 RCs.
<br><br>> 3) We call the Nov 22nd RC3 as the "KDE 4 Technology Platform<br>> Release". We then take the extra month afforded by the additional RCs<br>> for documentation, translations, unit tests, artwork and bugfixes ONLY
<br>> (deep freeze).<br><br>We should be in deep freeze mode with RC1.<br>I'd rather see another Beta4.<br><br>><br>> The new schedule would look like:<br>><br>> September 25: 3.94 (KDE 4.0 Beta3)<br>> October 23: Total Release Freeze
<br>> October 25: 3.96 (KDE 4.0 RC1)<br>> November 8: 3.97 (KDE 4.0 RC2)<br>> November 22: 3.98 (KDE 4.0 Technology Platform Release a.k.a. RC3)<br>> December 6: 3.99 (KDE 4.0 RC4)<br>> December 20: 4.0.0 tagged, is unannounced except to distros--
4.0.x<br>> branched, trunk unfreezes...<br>> January 17: 4.0.0 announcement and release party<br>><br><br>Counter proposal (give or take a day here or there):<br>September 25: 3.94 (KDE 4.0 Beta3)<br>October 25:
3.95 (KDE 4.0 Beta4)<br>November 20: Total Release Freeze<br>November 22: 3.97 (KDE 4.0 Technology Platform Release a.k.a. RC1)<br>December 6: 3.98 (KDE 4.0 RC2)<br>December 20: 4.0.0 tagged, is unannounced except to distros--
4.0.x<br>branched, trunk unfreezes...<br>January 17: 4.0.0 announcement and release party<br><br>> If anyone honestly believes that we'll need more than the<br>> extra two months, we will need to reschedule the release party now
<br>> before flights are booked.<br><br>Who can predict? Real life happens... it just happened to me and<br>I've been very unproductive for several weeks.<br><br>Hey, let's make a list of minimum requirements (a small list) that we
<br>absolutely must have done before tagging 4.0.0. Here's a start:<br> - a functional workspace<br> - oxygen style working<br> - konqueror working<br> - dolphin working<br> - sound working<br> - kmail working<br> - kate working
<br><br>-Allen<br></blockquote></div><br><br clear="all"><br>-- <br>Troy Unrau<br>Geophysics Student - University of Manitoba<br>KDE Gearhead