Page History

...

• Confirm that no one else is building the RC at the same time as you are. 
• Update your local git clone to the latest version of the code.
• Check the rebar.config.script file and look at all of the dependency version numbers. If any are raw git hashes (not x.x.x-style version numbers), tag those sub-repositories first. Then, update the rebar.config.script with these version numbers and commit the change. No dependencies should be referenced by a raw git hash.
• Run one final make check as in the first section of this process, being sure to run the git clean and git reset commands.
  

• If this is the first RC for a new major or minor release (3.0.0, 2.3.0, etc. but not 2.3.1) then create a branch:

  Code Block
  language bash
  $ git checkout -b #.#.x git push origin

  
  

• Tag this version with x.x.x-RC# where # represents which release candidate this is (1, 2, 3...):

  Code Block
  language bash
  $ git tag -a x.x.x-RC# -m "Version x.x.x-RC#" --sign $ git push origin --tagsx.x.x-RC#

   

• Build the release candidate tarball (substitute the correct number for the # below):

  Code Block
  language bash
  $ cd couchdb $ git reset --hard && git clean -ffdx $ ./configure --without-proper $ make dist

  
  

...

$ cd couchdb && git checkout x.x.x-RC#
$ git tag -a x.x.x -m "Version x.x.x" --sign
$ git push origin --tagsx.x.x

The release tarball can now be renamed:

...