Project

General

Profile

ReleaseProcess » History » Version 2

Eric Davis, 2010-06-28 04:48
Adding tag

1 1 Eric Davis
h1. ReleaseProcess
2
3
This page described the process for packaging up a new Redmine release.
4
5
h2. Stable branches
6
7
# Checkout the stable branch (e.g. 0.9-stable)
8
# 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*.
9
# Update the locales with @rake locales:update@
10
# Run the test suite to make sure there are no errors
11
# Checkout trunk again for these next steps
12
## Update the @doc/CHANGELOG@ to list the changes
13
## Check that @doc/INSTALL@ and @doc/UPGRADING@ are correct
14
## Increment the version number, @lib/redmine/version.rb@
15
# Checkout the stable branch again and merge these updates to it
16
# Freeze the current Rails version
17
# Package up Redmine into a zip and tar.gz. *Make sure no private configuration files are included*
18
# Create MD5 checksum files for the zip and tar.gz files
19 2 Eric Davis
# 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@
20 1 Eric Davis
# Upload the new release to "Rubyforge":http://rubyforge.org/projects/redmine/
21
# Create a release announcement for:
22
## Rubyforge
23
## Redmine.org
24
## Redmineblog.com