svn commit: r1412993 - /ode/site/trunk/content/release-guidelines.mdtext

[va...@apache.org]

Author: vanto
Date: Fri Nov 23 17:33:06 2012
New Revision: 1412993

URL: http://svn.apache.org/viewvc?rev=1412993&view=rev
Log:
markup fix.

Modified:
    ode/site/trunk/content/release-guidelines.mdtext

Modified: ode/site/trunk/content/release-guidelines.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/release-guidelines.mdtext?rev=1412993&r1=1412992&r2=1412993&view=diff
==============================================================================
--- ode/site/trunk/content/release-guidelines.mdtext (original)
+++ ode/site/trunk/content/release-guidelines.mdtext Fri Nov 23 17:33:06 2012
@@ -1,14 +1,15 @@
 Title: Release Guidelines
+
 <a name="ReleaseGuidelines-CheckList"></a>
 ## Check List
 
-These guidelines are extracted from the [incubator release guidelines](http://incubator.apache.org/guides/releasemanagement.html#rules) 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.
+These guidelines are extracted from the [incubator release guidelines](http://incubator.apache.org/guides/releasemanagement.html#rules) and other projects (like [Avalon](http://wiki.apache.org/avalon/AvalonReleaseManagerHowto)) 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.
 
 * 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.
-* The released archives should have "apache" and "incubating" in their naming.
+* The released archives should have "apache" and "ode" in their naming.
 * A release should include both a source and a binary package.
 * The source distro should include a BUILDING document.
-* make sure the RELEASE_NOTES are up to date (version number, list of issues, links to jira, etc)
+* make sure the RELEASE_NOTES are up to date (version number, list of issues, links to JIRA, etc)
 * Both distros should include a RELEASE_NOTES, the LICENSE
 * Different distribution types should unpack to directories with different names (say apache-ode-x.x and apache-ode-src-x.x).
 * Our releases don't include general documentation (only Javadoc) but a link to our website main documentation pages in the README.
@@ -35,11 +36,11 @@ Once the release has been cut, a vote sh
 ## Announcing The Release
 
 1. Perform a release in JIRA and create a new release version in JIRA
-1. Create a download page for the release in the WIKI
+1. Update the download page for the release on the Website
 1. Mail the dev & user lists, and announce@apache.org
-1. Post a news entry on the WIKI
+1. Post a news entry on the Website
 1. Have a beer!
 
 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.
 
-Announcements should be posted from the release manager's apache.org address.
+Announcements should be posted from the release manager's apache.org address.
\ No newline at end of file