lucy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [lucy-commits] [Lucy Wiki] Update of "ReleaseGuide" by MarvinHumphrey
Date Thu, 16 Dec 2010 01:23:39 GMT
Dear Wiki user,

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

The "ReleaseGuide" page has been changed by MarvinHumphrey.
The comment on this change is: Rework section for branching and tagging a release candidate..
http://wiki.apache.org/lucy/ReleaseGuide?action=diff&rev1=10&rev2=11

--------------------------------------------------

  
  Official Apache Lucy releases will have X.Y.Z style versions, but packaged/binary releases
of particular host language implementations (e.g. CPAN or rubygems) may append a final .n
to their versions (X.Y.Z.n) to indicate a change in packaging or distribution for that particular
package. See the discussion [[http://mail-archives.apache.org/mod_mbox/incubator-lucy-dev/201012.mbox/browser|here]].
  
+ = Branching and tagging a release candidate =
- = Branching =
- 
- Skip this section if this is NOT the first release in a series (i.e. release X.Y.0).
- 
-  1. Notify developers on the #lucy_dev IRC channel that you are about to branch a release.
- 
-  1. In trunk, update the CHANGES file with the anticipated release date.  Be sure to allow
enough time for both the PPMC and Incubator PMC votes to clear (6 days or so).
  
   1. Bump the $VERSION value to X.Y.Z.
  
+  1. Update the CHANGES file with the anticipated release date.  Be sure to allow enough
time for both the PPMC and Incubator PMC votes to clear (6 days or so).
+ 
-  1. Commit your changes to trunk.
+  1. Commit your changes.
   {{{
-  svn commit -m "Updating CHANGES and VERSION for release X.Y.Z"
+  svn commit -m "Updating CHANGES and version number for release X.Y.Z"
   }}}
  
-  1. Create a branch for the release series:
+  1. If this is the first release in a series (i.e. release X.Y.0), create a branch:
   {{{
   svn copy https://svn.apache.org/repos/asf/incubator/lucy/trunk \
-    https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-X.Y.Z -m "Branching for
X.Y.Z release"
+    https://svn.apache.org/repos/asf/incubator/lucy/branches/X.Y -m "Branching for X.Y.Z
release"
+  }}}
+ 
+  1. Create a tag for the release candidate.
+  {{{
+  svn copy https://svn.apache.org/repos/asf/incubator/lucy/branches/X.Y \
+    https://svn.apache.org/repos/asf/incubator/lucy/tags/X.Y.Z-rcN -m "Tagging release candidate
X.Y.Z-rcN"
   }}}
  
  = Building =
  
-  1. Export out a clean copy of the release branch:
+  1. Export out a clean copy from the release candidate tag:
   {{{
-  svn export https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-X.Y.Z
+  svn export https://svn.apache.org/repos/asf/incubator/lucy/tags/X.Y.Z-rcN lucy-X.Y.Z-rcN
   }}}
  
   2. Tar and gzip the export:
   {{{
-  tar -cf lucy-X.Y.Z-incubating.tar branch-X.Y.Z
+  tar -czf lucy-X.Y.Z-incubating.tar.gz lucy-X.Y.Z-rcN
-  gzip lucy-X.Y.Z-incubating.tar
   }}}
  
   3. Perform whatever quality control seems prudent on the .tar.gz file, installing it on
test system(s), etc.

Mime
View raw message