Author: linus
Date: 2008-09-28 01:25:40-0700
New Revision: 15816

Modified:
   trunk/www/release_plan.html

Log:
Moved the 0.26 releases last.

Modified: trunk/www/release_plan.html
Url: 
http://argouml.tigris.org/source/browse/argouml/trunk/www/release_plan.html?view=diff&rev=15816&p1=trunk/www/release_plan.html&p2=trunk/www/release_plan.html&r1=15815&r2=15816
==============================================================================
--- trunk/www/release_plan.html (original)
+++ trunk/www/release_plan.html 2008-09-28 01:25:40-0700
@@ -30,106 +30,6 @@
 <h2>Upcoming releases</h2>
 
 <div class="h3">
-<h3>ArgoUML release 0.26.alpha5</h3>
-<p>
-Planned date: 2008-08-26
-</p>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta1</h3>
-<p>
-Planned date: 2008-08-31
-</p>
-<p>
-If there are remaining P2 issues 
-this will be converted to an alpha release.
-</p>
-<ul>
-<li>Beginning of the beta period.
-    From this point on, it is not allowed to commit solutions to open issues
-    in the trunk for any of the involved project.
-    The release manager, Linus Tolke,
-    grants permission exceptions (i.e. for all commits in trunk).
-    </li>
-
-<li>A known problems list is compiled.</li>
-
-<li>All P1 and P2 issues must be solved.</li>
-</ul>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta2</h3>
-<p>
-Planned date: 2008-09-09
-</p>
-<ul>
-<li>If needed.
-</ul>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta3</h3>
-<p>
-Planned date: 2008-09-13
-</p>
-<p>
-This release was not performed.
-</p>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta3</h3>
-<p>
-New release planned.
-</p>
-<p>
-Planned date: 2008-09-18
-</p>
-<ul>
-<li>Issue 5384.
-<li>Issue 5389.
-<li>Issue 5393.
-<li>Issue 5395.
-<li>Issue 5388.
-</ul>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta4</h3>
-<p>
-New release planned.
-</p>
-<p>
-Planned date: 2008-09-21
-</p>
-<ul>
-<li>Issue 5360.
-</ul>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26.beta5</h3>
-<p>
-New release planned.
-</p>
-<p>
-Planned date: 2008-09-24
-</p>
-<ul>
-<li>Issue 5402.
-</ul>
-</div>
-
-<div class="h3">
-<h3>ArgoUML release 0.26</h3>
-<p>
-Planned date: 2008-09-27
-</p>
-</div>
-
-<div class="h3">
 <h3>ArgoUML release 0.27.1</h3>
 <p>
 Planned date: 2008-10-02
@@ -842,6 +742,106 @@
 </ul>
 </div>
 
+<div class="h3">
+<h3>ArgoUML release 0.26.alpha5</h3>
+<p>
+Planned date: 2008-08-26
+</p>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta1</h3>
+<p>
+Planned date: 2008-08-31
+</p>
+<p>
+If there are remaining P2 issues 
+this will be converted to an alpha release.
+</p>
+<ul>
+<li>Beginning of the beta period.
+    From this point on, it is not allowed to commit solutions to open issues
+    in the trunk for any of the involved project.
+    The release manager, Linus Tolke,
+    grants permission exceptions (i.e. for all commits in trunk).
+    </li>
+
+<li>A known problems list is compiled.</li>
+
+<li>All P1 and P2 issues must be solved.</li>
+</ul>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta2</h3>
+<p>
+Planned date: 2008-09-09
+</p>
+<ul>
+<li>If needed.
+</ul>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta3</h3>
+<p>
+Planned date: 2008-09-13
+</p>
+<p>
+This release was not performed.
+</p>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta3</h3>
+<p>
+New release planned.
+</p>
+<p>
+Planned date: 2008-09-18
+</p>
+<ul>
+<li>Issue 5384.
+<li>Issue 5389.
+<li>Issue 5393.
+<li>Issue 5395.
+<li>Issue 5388.
+</ul>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta4</h3>
+<p>
+New release planned.
+</p>
+<p>
+Planned date: 2008-09-21
+</p>
+<ul>
+<li>Issue 5360.
+</ul>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26.beta5</h3>
+<p>
+New release planned.
+</p>
+<p>
+Planned date: 2008-09-24
+</p>
+<ul>
+<li>Issue 5402.
+</ul>
+</div>
+
+<div class="h3">
+<h3>ArgoUML release 0.26</h3>
+<p>
+Planned date: 2008-09-27
+</p>
+</div>
+
 <hr>
 Last modified $Date$.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to