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 JanLehnardt
Date Thu, 10 Jan 2013 22:45:51 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 JanLehnardt:
http://wiki.apache.org/couchdb/Release_Procedure?action=diff&rev1=125&rev2=126

Comment:
link to email addresses of various mailing lists

  
  = Preparing the Community =
  
- Submit an RFC to the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list asking for a request for comments on the release.
+ Submit an RFC to the dev@couchdb.apache.org mailing list asking for a request for comments
on the release.
  
  Ask all developers to specifically check the `NEWS` and `CHANGES` file for anything that
has been added in this release.
  
@@ -201, +201 @@

  
  If they pass your own tests:
  
-  * [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/201202.mbox/%3CCA%2BY%2B444JKqhZvfZduqMmqaR1nCZU9Uvts_W9QCjxSfsnFdwmfA%40mail.gmail.com%3E|Call
a vote]] on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]] mailing
list.
+  * [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/201202.mbox/%3CCA%2BY%2B444JKqhZvfZduqMmqaR1nCZU9Uvts_W9QCjxSfsnFdwmfA%40mail.gmail.com%3E|Call
a vote]] on the dev@couchdb.apache.org mailing list.
   * Make sure to link to the [[Test_procedure|test procedure]] page.
-  * When the vote passes, send a [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/200907.mbox/%3C20090722214200.GA11737@tumbolia.org%3E|summary
of the vote]] to the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list.
+  * When the vote passes, send a [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/200907.mbox/%3C20090722214200.GA11737@tumbolia.org%3E|summary
of the vote]] to the dev@couchdb.apache.org mailing list.
  
  The vote email must include the full tree-ish used to prepare the release.
  
@@ -286, +286 @@

  
   * Copy the release directory to `/www/www.apache.org/dist/couchdb/releases` on `people.apache.org`.
    * Make sure that the release directory and all the files within it are owned by the `couchdb`
group and are group writable.
+  * Send a pre-announcement email to dev@couchdb.apache.org mailing list, so that downstream
distributors can prepare their own announcements.
   * Wait for all changes to be synced to public mirrors.
   * Update http://couchdb.apache.org/ to point to the new files.
-  * Send a pre-announcement email to [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list, so that downstream distributors can prepare their own announcements.
   * Update [[http://wiki.apache.org/couchdb/CurrentReleases|the wiki]] with the new release
information.
   * Wait for all changes to be synced to the public site.
   * Publish a blog post using the HTML version of the release notes.
-  * Send the [[http://s.apache.org/fR|release notes]] to the [[http://mail-archives.apache.org/mod_mbox/www-announce/|announce]],
[[http://mail-archives.apache.org/mod_mbox/couchdb-user/|couchdb-user]], and [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing lists.
+  * Send the [[http://s.apache.org/fR|release notes]] to the announce@apache.org, dev@couchdb.apache.org
and user@couchdb.apache.org mailing lists.
  
  At each stage of the actual release, it is expected that a person can follow the trail of
changes back to the source. Because most of these systems are slow, things must be done in
the correct order. It would be unfortunate if the website listed a release that was not available
on a local mirror, or that was missing a corresponding tag in the Git repository. The changes
should always propagate from the source, to the `dist` directory, to the mirrors, to `downloads.html`,
and finally to the actual release announcement.
  
@@ -308, +308 @@

     * Every current release should have one unreleased maintenance release open.
   * Update the links on this page to most recent email archives.
   * 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.
+  * Call a discussion on the dev@couchdb.apache.org mailing list about archiving old releases.
     * To archive an old release, remove it from [[http://wiki.apache.org/couchdb/CurrentReleases|the
wiki]] 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.
  
  = Useful Resources =

Mime
View raw message