Author: buildbot
Date: Fri Nov 23 17:33:13 2012
New Revision: 839343
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/release-guidelines.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 23 17:33:13 2012
@@ -1 +1 @@
-1412992
+1412993
Modified: websites/staging/ode/trunk/content/release-guidelines.html
==============================================================================
--- websites/staging/ode/trunk/content/release-guidelines.html (original)
+++ websites/staging/ode/trunk/content/release-guidelines.html Fri Nov 23
17:33:13 2012
@@ -83,13 +83,13 @@
<div class="span12">
<p><a name="ReleaseGuidelines-CheckList"></a></p>
<h2 id="check-list">Check List</h2>
-<p>These guidelines are extracted from the <a
href="http://incubator.apache.org/guides/releasemanagement.html#rules";>incubator
release guidelines</a> and other projects (like
[Avalon|http://wiki.apache.org/avalon/AvalonReleaseManagerHowto] or )
guidelines and are meant to be used as a reference for coming releases. It's
not really a todo list for the next release (that will be handled in Jira) but
a general list of things to have right and the places they're best
described.</p>
+<p>These guidelines are extracted from the <a
href="http://incubator.apache.org/guides/releasemanagement.html#rules";>incubator
release guidelines</a> and other projects (like <a
href="http://wiki.apache.org/avalon/AvalonReleaseManagerHowto";>Avalon</a>)
guidelines and are meant to be used as a reference for coming releases. It's
not really a todo list for the next release (that will be handled in JIRA) but
a general list of things to have right and the places they're best
described.</p>
<ul>
<li>Analyze the list of bugs left for this specific release. Assess whether
they're critical for the release or can be postponed to a subsequent
release.</li>
-<li>The released archives should have "apache" and "incubating" in their
naming.</li>
+<li>The released archives should have "apache" and "ode" in their naming.</li>
<li>A release should include both a source and a binary package.</li>
<li>The source distro should include a BUILDING document.</li>
-<li>make sure the RELEASE_NOTES are up to date (version number, list of
issues, links to jira, etc)</li>
+<li>make sure the RELEASE_NOTES are up to date (version number, list of
issues, links to JIRA, etc)</li>
<li>Both distros should include a RELEASE_NOTES, the LICENSE</li>
<li>Different distribution types should unpack to directories with different
names (say apache-ode-x.x and apache-ode-src-x.x).</li>
<li>Our releases don't include general documentation (only Javadoc) but a link
to our website main documentation pages in the README.</li>
@@ -110,9 +110,9 @@
<h2 id="announcing-the-release">Announcing The Release</h2>
<ol>
<li>Perform a release in JIRA and create a new release version in JIRA</li>
-<li>Create a download page for the release in the WIKI</li>
+<li>Update the download page for the release on the Website</li>
<li>Mail the dev & user lists, and [email protected]</li>
-<li>Post a news entry on the WIKI</li>
+<li>Post a news entry on the Website</li>
<li>Have a beer!</li>
</ol>
<p>Announcements should be signed by the release manager with the key used to
sign the release. Note that this may mean creating a plain text signature on
the machine used to sign the release and then transferring this.</p>
