[Lenya Wiki] Update of "ProjectReleaseHowTo" by BobHarner

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.

The following page has been changed by BobHarner:
http://wiki.apache.org/lenya/ProjectReleaseHowTo

The comment on the change is:
Added reminder to update Download pages with new release links

------------------------------------------------------------------------------
  
  ==  Release Schedule ==
  
- Users are encouraged to test the stable branch continously and report problems.
+ Users are encouraged to test the stable branch continuously and report problems.
  
   1. [OPTIONAL] Vote on making release, if there is no mid or long term release plan with already established release dates.
   2. '''Announce beginning of release/freeze''' along this schedule 7 days in advance including the actual freeze date. 
@@ -18, +18 @@

   4. '''Start testing''' the freezed code along the [wiki:TestCases test plan]. A '''test sprint on IRC''' is good for concentrated testing. ''The tests should be made on basis of a completely build Lenya binary distribution on Windows and Linux.'' It would be great, if we could make test installations available for the public and during the test sprint.
   5. '''New bugs''' found during 4 MUST be recorded in bugzilla. Bugs marked as CRITICAL or BLOCKER MUST be fixed before the release.
   6. Start at 4 again
-  7. If tests are ok, '''vote on to release''' immediately; on a positive vote summary, '''create a tag branch'''; svn copy from a branch to a tag e.g. lenya/branches/BRANCH_1_2_X to lenya/tags/RELEASE_1_2_1, lock down the tagged version e.g. lenya/tags/RELEASE_1_2_1, '''release, and publish a ProjectReleaseAnnouncement ''' to appropriate places:
+  7. If tests are ok, '''vote on to release''' immediately; on a positive vote summary, '''create a tag branch'''; svn copy from a branch to a tag e.g. lenya/branches/BRANCH_1_2_X to lenya/tags/RELEASE_1_2_1, lock down the tagged version e.g. lenya/tags/RELEASE_1_2_1, then '''release''' (see '''Platform independent notes''' below).
+  8. Edit the '''Downloads''' links on the web site with links to the new release files.  (Currently that's [http://svn.apache.org/repos/asf/lenya/docu/src/documentation/content/xdocs/index.xml index.xml] and [http://svn.apache.org/repos/asf/lenya/docu/src/documentation/content/xdocs/docs/1_2_x/installation/index.xml docs/1_2_x/installation/index.xml].)
+  9. Publish a ProjectReleaseAnnouncement to appropriate places:
     * Lenya website 
     * user@lenya.apache.org
     * users@cocoon.apache.org
@@ -30, +32 @@

     * http://www.contentmanager.net (via contact form)
     * http://www.javalobby.org/forums/post!default.jspa?forumID=17
     * http://www.theserverside.com/news/post.tss
-  8. Update the Lenya DOAP file (http://svn.apache.org/repos/asf/lenya/site/doap_Lenya.rdf) with the version and date of this new release.
+ 10. Update the Lenya DOAP file (http://svn.apache.org/repos/asf/lenya/site/doap_Lenya.rdf) with the version and date of this new release.
  
  === ISSUES ===
   * Try to find a day for the test sprint, where lots of devs are present.
  
- ==  Plattform independent notes ==
+ ==  Platform independent notes ==
   * compile a pristine cocoon with the local properties from lenya
   * Set property ''version'' in file ''src/targets/properties-build.xml'' to the appropriate Lenya version
   * regenerate INSTALL-src.txt and INSTALL-bin.txt with the appropriate XSLT

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org