Changes between Version 31 and Version 32 of Release/Procedure


Ignore:
Timestamp:
12/15/11 18:01:00 (6 years ago)
Author:
ahocevar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Release/Procedure

    v31 v32  
    1111http://www.geoext.org/trac/geoext/query?milestone=x.y&resolution=fixed&order=component
    1212}}}
    13  1. Based on the list from the previous step, create a wiki page for the new release. The page should be named ''Release/x.y/Notes''.  The release notes should contain a short description of added and modified features, with links to the respective documentation and tickets. Target audience is a GeoExt user.
    14  1. Create a new branch
     13 1. Make sure that no GitHub pull requests are open for this release's milestone, and see which were closed since the last milestone.
     14 1. Based on the lists from the previous two steps, create a wiki page for the new release. The page should be named ''Release/x.y/Notes''.  The release notes should contain a short description of added and modified features, with links to the respective documentation and tickets. Target audience is a GeoExt user.
     15 1. Create a new branch for both http://github.com/geoext/geoext and http://github.com/geoext/geoext-docsrc
    1516{{{
    16   svn copy -m "Branching for the x.y Release" http://svn.geoext.org/core/trunk http://svn.geoext.org/core/branches/x.y
     17  git branch x.y
     18  git checkout x.y
     19  git push upstream x.y
    1720}}}
    18  1. If this branch of GeoExt depends on something other than an OpenLayers tag, modify the {{{svn:externals}}} property for the branch to peg it to a specific OpenLayers revision (and commit the change to the branch).  E.g.:
    19 {{{
    20   openlayers -r9737 http://svn.openlayers.org/trunk/openlayers
    21 }}}
    22  1. Add the text from the release notes to the {{{geoext}}} directory in the branch (e.g. {{{geoext/release-notes.txt}}}).
    23  1. Set the ''release'' and ''version'' in http://svn.geoext.org/core/branches/x.y/docsrc/conf.py and commit the change
     21 1. In the new docsrc branch, set the ''release'' and ''version'' in conf.py and commit/push the change
    2422 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]]
    2523   1. Compile a Release Announcement. The announcement should be located at ''Release/x.y/Announce/RCZ'' and should include one of the following:
     
    2725     * 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):''
    2826{{{
    29 http://geoext.org/trac/geoext/query?status=closed&version=x.y+RCW&milestone=0.5&resolution=fixed&order=priority
     27http://geoext.org/trac/geoext/query?status=closed&version=x.y+RCW&milestone=x.y&resolution=fixed&order=priority
    3028}}}
    31    1. Add a link to the download (the file will be called GeoExt-x.y-rcZ.zip) and the release notes in http://svn.geoext.org/core/trunk/docsrc/downloads.rst and commit the change
    32    1. Set the ''release'' in http://svn.geoext.org/branches/x.y/trunk/docsrc/conf.py and commit the change
     29   1. In the docsrc branch, add a link to the download (the file will be called GeoExt-x.y-rcZ.zip) and the release notes in downloads.rst and commit/push the change
     30   1. In the docsrc branch, set the ''release'' in conf.py and commit the change
    3331   1. Set the "latest" release in http://svn.geoext.org/geoext/website/website-conf.cfg and commit the change
    34    1. Tag the release:
     32   1. Tag the release for both http://github.com/geoext/geoext and http://github.com/geoext/geoext-docsrc:
    3533{{{
    36   svn copy -m "Tagging the x.y rcZ Release" http://svn.geoext.org/core/branches/x.y http://svn.geoext.org/core/tags/release-x.y-rcZ
    37 }}}
    38    1. Build the distribution (assuming you have python, sqlite and jstools installed, otherwise follow the [http://svn.geoext.org/core/trunk/geoext/build/readme.txt build] and [http://svn.geoext.org/website/README.txt website] instructions:
     34  git tag release-x.y-rcZ
     35  git push --tags
     36 }}}
     37   1. Build the distribution (assuming you have python, sqlite and jstools installed:
    3938{{{
    4039  svn checkout http://svn.geoext.org/website GeoExt
     
    4544}}}
    4645
    47    1. Upload GeoExt-x.y-rcZ.zip from your current directory to http://geoext.org/trac/geoext/wiki/Download
    48    1. Add a new hosted version on http://api.geoext.org (Note: we do not create release candidate APIs. As soon as we have a release candidate, we populate http://api.geoext.org/x.y/):
     46   1. Upload GeoExt-x.y-rcZ.zip from your current directory to http://github.com/geoext/geoext/downloads
     47   1. Update the release website and add a new hosted version on http://api.geoext.org (Note: we do not create release candidate APIs. As soon as we have a release candidate, we populate http://api.geoext.org/x.y/):
    4948{{{
    5049  ssh admin@www.geoext.org
    5150  sudo su - www-data
    5251  cd /var/www/api.geoext.org/htdocs/
    53   curl "http://trac.geoext.org/attachment/wiki/Download/GeoExt-x.y-rcZ.zip?format=raw" > GeoExt.zip
    54   unzip GeoExt.zip
     52  wget "http://github.com/downloads/geoext/geoext/GeoExt-x.y-rcZ.zip"
     53  unzip GeoExt-x.y-rcZ.zip
     54  rm -Rf /var/www/www.geoext.org/htdocs/website/*
     55  cp -Rf GeoExt/docs/* /var/www/www.geoext.org/htdocs/website/
    5556  mv GeoExt x.y
    56   rm GeoExt.zip
     57  rm GeoExt-x.y-rcZ.zip
    5758}}}
    5859   1. Create a new ''Version'' entry in TRAC called "x.y RCZ" for bug tracking[[br]][[br]]
     
    8889http://geoext.org/trac/geoext/query?group=component&milestone=x.y&resolution=fixed&order=priority
    8990}}}
    90  1. Add a link to the download (the file will be named GeoExt-x.y.zip) and the release notes in http://svn.geoext.org/core/branches/x.y/docsrc/downloads.rst and commit the change
    91  1. Set the ''release'' in http://svn.geoext.org/core/branches/x.y/docsrc/conf.py and commit the change
     91 1. In the docsrc branch, add a link to the download (the file will be named GeoExt-x.y.zip) and the release notes in downloads.rst and commit/push the change
     92 1. In the docsrc branch, set the ''release'' in conf.py and commit/push the change
    9293 1. Set the "latest" release in http://svn.geoext.org/geoext/website/website-conf.cfg and commit the change
    93  1. Tag the release:
     94 1. For both http://github.com/geoext/geoext and http://github.com/geoext/geoext-docsrc, tag the release:
    9495{{{
    95   export VERSION=x.y
    96   svn copy -m "Tagging the Final $VERSION Release" http://svn.geoext.org/core/branches/$VERSION http://svn.geoext.org/core/tags/release-$VERSION
     96  git tag x.y
     97  git push --tags
    9798}}}
    9899 1. Build the distribution (assuming you have already checked out http://svn.geoext.org/website to GeoExt):
     
    103104}}}
    104105
    105  1. Upload GeoExt-x.y.zip from your current directory to http://geoext.org/trac/geoext/wiki/Download
    106  1. Add a new hosted version on http://api.geoext.org:
     106 1. Upload GeoExt-x.y.zip from your current directory to http://github.com/geoext/geoext/downloads
     107   1. Update the release website and add a new hosted version on http://api.geoext.org:
    107108{{{
    108109  ssh admin@www.geoext.org
    109110  sudo su - www-data
    110111  cd /var/www/api.geoext.org/htdocs/
    111   curl "http://trac.geoext.org/attachment/wiki/Download/GeoExt-x.y.zip?format=raw" > GeoExt.zip
    112   unzip GeoExt.zip
     112  wget "http://github.com/downloads/geoext/geoext/GeoExt-x.y.zip"
     113  unzip GeoExt-x.y.zip
     114  rm -Rf /var/www/www.geoext.org/htdocs/website/*
     115  cp -Rf GeoExt/docs/* /var/www/www.geoext.org/htdocs/website/
    113116  mv GeoExt x.y
    114   rm GeoExt.zip
     117  rm GeoExt-x.y.zip
    115118}}}
    116  1. Add a link to the download (the file will be named GeoExt-x.y.zip) and the release notes in http://svn.geoext.org/core/trunk/docsrc/downloads.rst and commit the change
    117  1. Set the ''release'' and "version" in http://svn.geoext.org/core/trunk/docsrc/conf.py and commit the change
    118  1. Add a link to the download (GeoExt-x.y.zip) and the release notes in http://svn.geoext.org/core/trunk/docsrc/downloads.rst and commit the change
     119 1. Merge the docsrc branch into docsrc master:
     120{{{
     121  git checkout master
     122  git merge release-x.y
     123  git push upstream master
     124}}}
    119125 1. Create a new ''Version'' entry in TRAC called "x.y + 1" for bug tracking.
    120126 1. Set the milestone "x.y" as completed:
    121127{{{
    122 ssh admin@www.geoext.org
    123 sudo su - www-data
    124 trac-admin /srv/trac/projects/geoext/ milestone completed x.y now
     128  ssh admin@www.geoext.org
     129  sudo su - www-data
     130  trac-admin /srv/trac/projects/geoext/ milestone completed x.y now
    125131}}}
    126132 1. Email the dev and users lists and announce the release containing: