ReleaseProcess » History » Revision 2
Revision 1 (Eric Davis, 2010-06-28 04:22) → Revision 2/10 (Eric Davis, 2010-06-28 04:48)
h1. ReleaseProcess This page described the process for packaging up a new Redmine release. h2. Stable branches # Checkout the stable branch (e.g. 0.9-stable) # Check that all of this releases' issues have been merged into the stable branch. The Resolved status is used to mark which issues still *need to be merged*. # Update the locales with @rake locales:update@ # Run the test suite to make sure there are no errors # Checkout trunk again for these next steps ## Update the @doc/CHANGELOG@ to list the changes ## Check that @doc/INSTALL@ and @doc/UPGRADING@ are correct ## Increment the version number, @lib/redmine/version.rb@ # Checkout the stable branch again and merge these updates to it # Freeze the current Rails version # Package up Redmine into a zip and tar.gz. *Make sure no private configuration files are included* # Create MD5 checksum files for the zip and tar.gz files # Tag the latest code in svn. e.g @svn cp svn+ssh://rubyforge.org/var/svn/redmine/branches/0.9-stable svn+ssh://rubyforge.org/var/svn/redmine/tags/0.9.5@ # Upload the new release to "Rubyforge":http://rubyforge.org/projects/redmine/ # Create a release announcement for: ## Rubyforge ## Redmine.org ## Redmineblog.com