Changes between Version 93 and Version 94 of Release/Procedure

Timestamp:

06/27/12 14:48:11 (11 months ago)

Author:

erilem

Comment:

--

Release/Procedure

@@ -177 +177 @@
  * Write a 50 word summary of the release and send to news_item at osgeo dot org
  * Change topic on IRC ({{{/topic}}})
-
-''' OLD AFTER THIS '''
-
-== Creating a Release Candidate ==
-
- 1. '''Release Candidate (RC) Cycle''' [[br]]''Let us say that for the RC in question, '''Z''' is the incremental release candidate number (starting with 1)''[[br]][[br]]
-   1. Compile a Release Announcement. The announcement should be located at ''Release/x.y/Announce/RCZ'' and should include one of the following:
-     * If this is the first RC (Z is 1): A link to the ''Release/x.y/Notes'' wiki, and a brief summary of its contents.
-     * If this is ''not'' the first RC, then: A brief summary of all of the tickets that were fixed in the last RC.[[br]] ''This should be a summary of the following trac query (where we let W be the previous RC number, i.e. Z-1):''
-{{{ 
-http://trac.openlayers.org/query?status=closed&version=x.y+RCW&milestone=x.y+Release&resolution=fixed&order=priority
-}}}
-    1. Set VERSION_NUMBER in http://svn.openlayers.org/branches/openlayers/x.y/lib/OpenLayers.js and http://svn.openlayers.org/branches/openlayers/x.y/lib/OpenLayers/SingleFile.js to "Release x.y-rcZ" and commit the change.
-    1. Create a release tag for the RC (off the release branch):
-
-  1. Export and Build the single file versions: 
-{{{
-$ wget -O release-x.y-rcZ.tar.gz https://github.com/openlayers/openlayers/tarball/release-x.y-rcZ
-$ tar xvzf release-x.y-rcZ.tar.gz
-$ cd openlayers-openlayers-*/tools
-$ VERSION=x.y-rcZ ./release.sh
-}}}
-
-'''UNCHANGED AFTER THIS LINE'''
-
-   1. Create a new API release directory on openlayers.org and install the build
-{{{
-  mkdir /www/openlayers/docs/api/x.y-rcZ
-  cd ..
-  cp build/OpenLayers.js /www/openlayers/docs/api/x.y-rcZ
-  cp -a img/ /www/openlayers/docs/api/x.y-rcZ
-  cp -a theme/ /www/openlayers/docs/api/x.y-rcZ
-}}}
-   1. Build the tarball and copy it up to openlayers.org
-{{{
-  # First remove all .pyc files from the directory.
-  rm tools/*.pyc
-  cd ..
-  tar cvfz OpenLayers-x.y-rcZ.tar.gz OpenLayers-x.y-rcZ/
-  cp OpenLayers-x.y-rcZ.tar.gz /www/openlayers/docs/download
-}}}
-   1. Build a zip archive to openlayers.org
-{{{
-  zip -9r OpenLayers-x.y-rcZ.zip OpenLayers-x.y-rcZ/
-  cp OpenLayers-x.y-rcZ.zip /www/openlayers/docs/download
-}}}
-   1. Create a new ''Version'' entry in TRAC called "x.y RCZ" for bug tracking[[br]][[br]]
-   1. Email the Release Announcement to the dev list.[[br]][[br]]
-
-== The Testing Cycle ==
-
-   1. '''Testing Cycle''' -- in which users and developers:
-      * Report new tickets 
-        1. Milestone: ''x.y Release'' 
-        1. Version: ''x.y RCZ''
-      * Fix outstanding tickets:
-        1. Commit only to trunk
-        1. Set 'State' to 'Pullup' as they still need to be pulled up to the branch
-        1. Do not mark as ''closed'' (i.e. leave them open)
-      * Run all tests in both Firefox 1.5 and IE 6.
-        * If any tests fail, return to '''Testing Cycle''' and report a new ticket.
-        * If all tests pass, a committer may send a proposal email to the dev list calling for:
-          * A new RC:
-            1. The support of at least one other committer must be obtained.
-            1. The committer chooses which patches to include in the the new RC or Final Release. [[br]] ''These should be taken from the the results of the following trac query:''
-{{{
-http://trac.openlayers.org/query?milestone=x.y+Release&keywords=%7Epullup&order=priority
-}}}
-              1. Bring up each ticket's patch from trunk into the branch
-              1. Change each ticket's 'State' field to 'Complete'
-              1. Add brief summary of the change to the ''Release/x.y/Notes'' wiki
-              1. Mark ticket ''closed''
-            1. Committer exits '''Testing Cycle''', starts new '''Release Candidate Cycle'''
-          * The Final Release:
-            1. All tickets for the milestone must be closed in the previous RC and no new tickets opened in the current one.
-            1. A successful [wiki:SteeringCommittee#DetailedProcess voting] round must pass the SteeringCommittee.
-            1. SteeringCommittee member exits the '''Testing Cycle''' and '''Release Candidate Cycle''' and proceeds to the next step, '''Review the ''Release/x.y/Notes'' wiki...'''[[br]][[br]]
- 1. Review the ''Release/x.y/Notes'' wiki and make sure it contains important info from all the closed tickets for the ''Release x.y'' milestone:
-{{{
-http://trac.openlayers.org/query?group=component&milestone=x.y+Release&resolution=fixed&order=priority
-}}}
- 1. Update news.txt: both in trunk and in the branch, update the /news.txt file to reflect this release. Note that you must be both tricky and quick here, as you must *predict* the correct revision number for the actual tagging of the release, which you will do in the next step. Essentially, this is current release +2 (one for the check-in of news.txt, one for the tag). It seems absurd, but it is good to make sure that no one else is checking in at the same time as this maneuver assumes a quiet wire.
-    1. Set VERSION_NUMBER in http://svn.openlayers.org/branches/openlayers/x.y/lib/OpenLayers.js and http://svn.openlayers.org/branches/openlayers/x.y/lib/OpenLayers/SingleFile.js to "Release x.y-rcZ" and commit the change.
-  1. Tag the release:
-{{{
-  export VERSION=2.7
-  svn copy -m "Tagging the Final x.y Release" http://svn.openlayers.org/branches/openlayers/$VERSION http://svn.openlayers.org/tags/openlayers/release-$VERSION
-}}}
- 1. Export and Build the single file version: 
-{{{
-  svn export http://svn.openlayers.org/tags/openlayers/release-$VERSION OpenLayers-$VERSION
-  cd OpenLayers-$VERSION/build
-  ./build.py
-}}}
- 1. Create a new API release directory on openlayers.org and install the build
-{{{
-  mkdir /www/openlayers/docs/api/$VERSION
-  cd ..
-  cp build/OpenLayers.js /www/openlayers/docs/api/$VERSION
-  cp -a img/ /www/openlayers/docs/api/$VERSION
-  cp -a theme/ /www/openlayers/docs/api/$VERSION
-}}}
- 1. Build the tarball and copy it up to openlayers.org
-{{{
-  # First remove all .pyc files from the directory.
-  rm tools/*.pyc
-  # move single file version
-  cp build/OpenLayers.js OpenLayers.js
-  rm build/OpenLayers.js
-  
-  cd ..
-  mkdir OpenLayers-$VERSION/doc/devdocs
-  perl ~crschmidt/NaturalDocs -i OpenLayers-$VERSION/lib -o HTML OpenLayers-$VERSION/doc/devdocs -p OpenLayers-$VERSION/doc_config -s Default OL
-  mkdir OpenLayers-$VERSION/doc/apidocs
-  perl ~crschmidt/NaturalDocs -i OpenLayers-$VERSION/lib -o HTML OpenLayers-$VERSION/doc/apidocs -p OpenLayers-$VERSION/apidoc_config -s Default OL
-
-  tar cvfz OpenLayers-$VERSION.tar.gz OpenLayers-$VERSION/
-  cp OpenLayers-$VERSION.tar.gz /www/openlayers/docs/download
-}}}
- 1. Build a zip archive to openlayers.org
-{{{
-  zip -9r OpenLayers-$VERSION.zip OpenLayers-$VERSION/
-  cp OpenLayers-$VERSION.zip /www/openlayers/docs/download
-}}}
- 1. Install the new API code on openlayers.org
-{{{  
-  export X=2
-  ln -sf /www/openlayers/docs/api/$VERSION/OpenLayers.js /www/openlayers/docs/api
-  ln -sf /www/openlayers/docs/api/$VERSION/img /www/openlayers/docs/api
-  ln -sf /www/openlayers/docs/api/$VERSION/theme /www/openlayers/docs/api
-  rm /www/openlayers/docs/api/$VERSION && ln -sf /www/openlayers/docs/api/$VERSION /www/openlayers/docs/api/$X
-}}}
- 1. Create a new ''Version'' entry in TRAC called "x.y" for bug tracking.[[br]][[br]]
- 1. Update HowToDownload wiki with new latest stable api release links. [[br]][[br]]
- 1. Email the dev and users lists and announce the release containing:
-   * A link to the ''Release/x.y/Notes'' wiki 
-   * A summary of the major features and bug fixes for the release
- 1. Write a 50 word summary of the release and send to news_item at osgeo dot org