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, 30 Mar 2013 12:48:16 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=192&rev2=193

  
  Replace `CANDIDATE` with the candidate you are building from.
  
- Now, follow these steps:
- 
-  * ''Go back to the release notes section and complete the rest of the process.''
+ ''Go back to the release notes section and complete the rest of the process.''
-  * 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.
+ 
+ Choose a date for the release. Tuesdays mornings PST are better, because they get more press
coverage.
+ 
+ Open this file:
+ 
+ {{{
+ email/schedule_release.txt
+ }}}
+ 
+ Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
+ 
+ (You should replace values as necessary.)
+ 
+ Copy the HTML version of the release notes, and [[https://blogs.apache.org/roller-ui/login.rol|draft
a blog post]], but do not publish yet.
+ 
+ Wait for the scheduled release time, or until all the release files have been synced to
the public mirrors.
+ 
-  * Update http://couchdb.apache.org/ to point to the new files.
+ Update http://couchdb.apache.org/ to point to the new files.
+ 
-  * Update [[http://wiki.apache.org/couchdb/CurrentReleases|the wiki]] with the new release
information.
+ 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.
+ 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 announce@apache.org, dev@couchdb.apache.org
and user@couchdb.apache.org mailing lists.
+ 
+ Publish the blog post.
+ 
+ Copy the text version of the release notes into an email, and send to the following lists:
+ 
+  * announce@apache.org
+  * announce@couchdb.apache.org
+  * user@couchdb.apache.org
+  * dev@couchdb.apache.org
+ 
+ The subject should be:
+ 
+ {{{
+ [ANNOUNCE] Apache CouchDB VERSION has been released
+ }}}
+ 
+ Replace `VERSION` with the version you are building from.
  
  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.
  

Mime
View raw message