couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Release_procedure" by NoahSlater
Date Sat, 07 Apr 2012 21:24:30 GMT
Dear Wiki user,

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

The "Release_procedure" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Release_procedure?action=diff&rev1=109&rev2=110

   * Update the `NEWS` and `CHANGES` files with important information.
   * Add note about breaking changes to the `NEWS` file if necessary.
   * Remove "version has not been released" warnings from `NEWS` and `CHANGES` if present.
-  * If working on a branch, make sure `NEWS` and `CHANGES` are synced with trunk.
+  * If working on a branch, make sure `NEWS` and `CHANGES` are synced with master.
   * Update the `acinclude.m4.in` file with version information.
     * LOCAL_VERSION_MAJOR should be the X in X.Y.Y
     * LOCAL_VERSION_MINOR should be the X in Y.X.Y
     * LOCAL_VERSION_REVISION should be the X in Y.Y.X
     * LOCAL_VERSION_STAGE must always be empty on a release tag.
-      * When this is set, it indicates a development version. It is set on branches or on
trunk so that the release number includes the source code revision number, which can be useful
for development builds.
+      * When this is set, it indicates a development version. It is set on branches or on
master so that the release number includes the source code revision number, which can be useful
for development builds.
   * Update the [[Breaking_changes]] document.
  
  = Preparing the Community =
@@ -276, +276 @@

  
  = Doing Housekeeping =
  
-  * Add a new release section to `NEWS` and `CHANGES` on trunk if not already present.
+  * Add a new release section to `NEWS` and `CHANGES` on master if not already present.
   * Add a new release section to `NEWS` and `CHANGES` on Y.Y.x the branch if not already
present.
   * Add "version has not been released" warnings to these release sections if not already
present.
   * [[https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310780|Update
versions]] in JIRA.
     * If the currently released version is 0.1.0, JIRA should have options for 0.1.1, 0.2.0,
and 0.3.0.
     * The released version should be marked as released in JIRA.
   * Update the links on this page to most recent email archives.
-  * Update branches, trunk, and site with security changes not documented in the released.
+  * Update branches, master, and site with security changes not documented in the released.
   * Call a discussion on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list about archiving old releases.
     * To archive an old release, remove it from `downloads.html` and then delete the corresponding
directory from the `dist` directory. Do not worry about the release artefacts no longer being
available, they are automatically mirrored to the Apache archive site and will remain there
even after they are deleted from the main `dist` directory.
  

Mime
View raw message