[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    developer.kde.org/development-versions
From:       Stephan Kulow <coolo () kde ! org>
Date:       2005-09-29 7:58:58
Message-ID: 1127980738.050499.32363.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 465219 by coolo:

After the feedback I received, I decided this: We do a 3.4.3
first


 M  +6 -0      kde-3.4-release-plan.html  
 M  +17 -6     kde-3.5-release-plan.html  


--- trunk/developer.kde.org/development-versions/kde-3.4-release-plan.html \
#465218:465219 @@ -70,6 +70,12 @@
 
     <h3><b>Wednesday July 27th, 2005: Targeted 3.4.2 Release date</b></h3>
 
+    <h3><b>Wednesday October 5th, 2005: Creating tags/KDE/3.4.3/</b></h3>
+    The third translation and bug fix release.
+    Please add your changes to <a \
href="http://www.kde.org/announcements/changelogs/changelog3_4_2to3_4_3.php">trunk/www/announcements/changelogs/changelog3_4_2to3_4_3.php</a>.
 +
+    <h3><b>Wednesday October 12th, 2005: Targeted 3.4.3 Release date</b></h3>
+
     <h2><b>Frequently Asked Questions</b></h2>
 
     <h4>What's the deal with that feature-plan?</h4>
--- trunk/developer.kde.org/development-versions/kde-3.5-release-plan.html \
#465218:465219 @@ -30,19 +30,30 @@
     After this date the same message freeze applies as for released versions
    (i.e. only previously untranslated strings or clear errors in strings can be \
fixed - no new strings)  
-    <h3><b>September 10th, 2005: tags/KDE/3_5_beta1 created</b></h3>
+    <h3><b>September 10th, 2005: tags/KDE/3.5-beta1 created</b></h3>
     The 3.5 branch is tagged as Beta 1 and is frozen for nonurgent commits till \
14th.  
     <h3><b>September 13th, 2005: Beta1 is prepared</b></h3>
     Beta 1 is prepared and released after some initial testing.
     The incoming bugs will be reviewed for their severity.
 
-    <h3><b>After that?</b></h3>
-    We don't know yet how things develop and the Akademy event might change \
                something unforseen. So 
-    I would prefer to leave it open if we have a second beta or release right after \
                beta1. I would
-    guess, we don't need a second one for KDE 3.5. So the targeted release day would \
                be towards end
-    of october (4 weeks of giving beta1 testing, one or two weeks for RCs - release)
+    <h3><b>October 9th, 2005: tags/KDE/3.5-beta2 created</b></h3>
+    The 3.5 branch is tagged as Beta 2 and is frozen for nonurgent commits till \
12th.  
+    <h3><b>October 12th, 2005: Beta2 is prepared</b></h3>
+    Beta 2 is prepared and released after some initial testing.
+    The incoming bugs will be reviewed for their severity.
+
+    <h3><b>November 7th, 2005: Total release freeze</b></h3>
+    This is the very last for commiting anything that isn't reviewed on the
+    development lists. If in doubt, ask the release coordinator.
+
+    <h3><b>November 9th, 2005: Release Candidate 1</b></h3>
+    We will release 3.5.0 as first release candidate and then wait for show stoppers
+    to appear.
+
+    <h3><b>November 23rd, 2005: Targetted Release Date</b></h3>
+
     <h2><b>Frequently Asked Questions</b></h2>
 
     <h4>What's the deal with that feature-plan?</h4>


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic