Differences between revisions 5 and 6
Revision 5 as of 2013-07-22 16:47:01
Size: 2490
Comment: Add link to version-targeted issues.
Revision 6 as of 2013-08-23 15:33:18
Size: 2484
Comment: NEWS and CHANGES are dead.
Deletions are marked like this. Additions are marked like this.
Line 34: Line 34:
   * Check NEWS and CHANGES and make sure they are up-to-date with respect to new changes    * Check changelog.rst and make sure they are up-to-date with respect to new changes
Line 38: Line 38:
   * Check NEWS and CHANGES and make sure they are up-to-date with respect to new changes    * Check changelog.rst and make sure they are up-to-date with respect to new changes

The official documentation has moved to http://docs.couchdb.org — The transition is not 100% complete, but http://docs.couchdb.org should be seen as having the latest info. In some cases, the wiki still has some more or older info on certain topics inside CouchDB.

You need to be added to the ContributorsGroup to edit the wiki. But don't worry! Just email any Mailing List or grab us on IRC and let us know your user name.

Release Preparation

This is a work in progress. Please contribute to it and make it better.

Early in the cycle: early landings

  • See if we have bundled dependencies that need updating
    • ibrowse
    • mochiweb
    • jQuery
    • snappy
    • erlang-oauth

~1 week before release: ascertain good shape

~2 days before release: prepare change log

  • Go through code on the master and check for any changes since last release
    • @@ Can someone provide a Git command that will do this?

    • Check changelog.rst and make sure they are up-to-date with respect to new changes
  • Go through code on the last release branch and check for any changes since last release
    • (Is this needed? Why would we ever merge directly to the release branch outside of doing a release?)
    • @@ Can someone provide a Git command that will do this?

    • Check changelog.rst and make sure they are up-to-date with respect to new changes

Merging Fixes Into Master

This is also the time to consider whether you have any fixes that could land in master. If you've been working on a branch, please review your changes, and merge in anything that seems appropriate.

You can review your changes against master by running:

  • git log --abbrev-commit --pretty=oneline FROM..TO

@@ Is this correct?

If you can think of any other command that would help, or any tooling we might want to make, please update this page. I'd like this page to make things as easy as possible for people to just run a few commands and get the right stuff merged into the right places.

Release_Preparation (last edited 2013-08-23 15:33:18 by DirkjanOchtman)