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_Preparation" by NoahSlater
Date Tue, 16 Jul 2013 22:50:11 GMT
Dear Wiki user,

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

The "Release_Preparation" page has been changed by NoahSlater:
https://wiki.apache.org/couchdb/Release_Preparation

New page:
<<Include(EditTheWiki)>>

= Release Preparation =

<<TableOfContents(2)>>

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

== Auditing The Code ==

 * 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 NEWS and CHANGES 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 NEWS and CHANGES 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.

== Merging Pull Requests and Patches ==

This is also a good time to review an JIRA tickets that have patches that are just waiting
for a committer to apply them. If you are a committer, please apply the patches and close
out the ticket. If you're not a committer, please alert someone so they can do this for you.

''@@ What is a good URL for a search for tickets like this?''
 
Please also review our pull requests on GitHub:

    https://github.com/apache/couchdb/pulls

== Identifying the Type of Release ==

Once all this has been done, you must identify the type of release.

 * If there are breaking changes, you must bump the major version number
 * If there are new features, you must bump the minor version number
 * Otherwise, bump the patch number

== Merging master Into A Release Branch ==

If this is a patch release, master should be merged into the appropriate release branch.

Otherwise, you should create a brand new release branch.

Mime
View raw message