bzr-eclipse team mailing list archive
-
bzr-eclipse team
-
Mailing list archive
-
Message #00024
Doing a 1.2.0 release
Hi team, We're all keen to get a release out the door, so here's
a plan:
1] Let's agree versions
1.2.0 for bzr-eclipse
1.2.0 for bzr-java-lib
0.9.0 for bzr-xmloutput
2] Finalise our license status, we should be able to do a clean
EPL release.
3] Write a ChangeLog for each project. Piotr has done a lot of
the work there already.
In future, when committing a change, let's be sure to always
have the bug number in the commit message, and then put the
revision number into the bug report.
4] Write a release process, all the sites to update, the steps to
publish the release, update bug reports. I will take on this
task.
5] Fix or push the last bugs, everything with milestone 1.2
should be "Fix Committed" state.
and
6] Do the release
7] Start work on 1.2.1 which is a pure bug-fix release, in
anticipation of people using it and reporting issues, so that
we can be responsive.
Alex
--
idereal | deliver http://idereal.co.nz/
Get your software to market sooner 022 659 0282
Follow ups
References