bzr-eclipse team mailing list archive
-
bzr-eclipse team
-
Mailing list archive
-
Message #00005
Re: bzr-eclipse development
That is a very nice lise of improvements.
As I look at them I'll provide specific feedback where appropriate.
> 4), 5), 6) and 8) depend on changes in xmloutput plugin, some patches
> still need to be reviewed and pushed.
This is a pain, since installation needs to be done separately.
I'd suggest putting as much into this release as possible, to
hopefully avoid more changes in the near future.
Ideally bzr-eclipse will fail gracefully if an older version of
xmloutput is installed.
> I would be grateful for any comments and the information on what (and
> how) needs to be done to release a new version.
> I can host an update site, however, this will most likely require
> changes in Eclipse marketplace and other places that point to the
> current update site location.
I suggest a release process like this, for all three packages
together, bzr-eclipse, bzr-xmloutput, bzr-java-lib:
1] Identify functionality to include. This should be everything
done so far that's stable. You've done a good job of that.
2] Choose a new version number for the release, and create a
milestone in launchpad.
3] Go through all the bugs, fixing those we can and setting the
appropriate target milestone.
4] Do a beta release. (Beta is important because our testing and
packaging is not well exercised.)
4a] Update version in the code
4b] Update documentation (changelog)
4c] Build beta packages and make them available for download.
4d] Update the project pages for the new version.
4e] Update bug reports to indicate that bugs are released. (This
notifies people and encourags them to try the beta.)
5] Fix any bugs that are reported against the beta packages.
6] Either do another beta release as in step 4], or follow those
same steps for a final release.
Since this is a feature release, and the first one in a while, I
suggest for version numbers:
bzr-eclipse: 1.2.0
bzr-java-lib: 1.2.0 (Synchronise them, because they can be
installed together easily)
bzr-xml-output: 0.9.0 (jumping to 1.0.0 might be good too)
Beta versions could be:
1.2.0-beta or 1.2.0-rc1
Alex
--
hsh: The {Human|Happy|History} shell http://www.nongnu.org/hsh/
DEvelopment REFined - Enabling your software team - http://deref.co.nz/
PGP: ID: 0x23DC453B FPR: 42D0 66C2 9FF8 553A 373A B819 4C34 93BA 23DC 453B
Ironic humor dragged down all the twilight minarets he reared . . .
Follow ups
References