-
Notifications
You must be signed in to change notification settings - Fork 7
Release
Matt West edited this page Oct 27, 2012
·
1 revision
- summary All information regarding the release management.
- labels Phase-Design,Phase-Implementation,Phase-QA,Phase-Deploy
In order to get a better and more stable code we try to formalize the release management.
# After a new version has been released the next version is planed. All issues that should be solved in the next version will be given the milestone "next-release" # The leader will keep an eye on the list and will give a message in the [http://dev.simpleinvoices.org/ dev forum] when he sees that all issues of this milestone are solved or will be solved in the next few days. # The last preparations before the release can be done then.
A release will only happen if no PHP related errors are present in the code. In order to test this the following code is called in the root directory of the project:
# When the code is ready a new "tag" is set on the current trunk version. The tag will have the same name is the version (e.g. 2011-1).
Justin: Please write more about how this version number is set up.
# The tag will then be exported from Subversion to a directory on the local computer.
# This directory will then be zipped and uploaded to the Downloads-section on Google Code.
# get john from teammc to do a windows version
# The windows version name will correspond to the simple invoices version, If updates/fixes are needed for the program and not for si then the new release's version will have "fix-1" added to it name.
# update windows release package with new si stable from google code
# The windows version will then be zipped and uploaded to the Downloads-section on Google Code as well.
# Mark the two new packages as featured and the old ones as deprecated.
# Inform everyone about the new release
* announce on forum
* announce on blog
* announce on email lists
Then continue with the planning again.