I have now tagged the java/source tree 'keoe'. For what it's worth
this corresponds to the numbered releases
STIL v2.6
STILTS v1.2-1
TOPCAT v2.2-1
Following practice in the non-java parts of the tree, I have not
started a branch at this point.
On Thu, 3 Aug 2006, Tim Jenness wrote:
> It's possibly I'm being naive too. My intention was to simply do a
> checkout using the keoe tag (which I've done) and then let cvs
> automatically apply commits relative to that tag. I wa shaving trouble
> distinguishing that behaviour from an actual branch. Admittedly I haven't
> tried that yet.
I must admit I don't follow what you mean by "letting cvs automatically
apply commits relative to that tag". I plan to continue development
on the trunk as normal for java/source now; doing a checkout with the
tag keoe will give you the files frozen just now which I believe to
be ready for release, so that should be OK. However I don't know
what you want me to do if I manage to make some progress with the
GAIA build problem - I can commit any such changes on the trunk,
which is probably a good idea in any case, but doing a checkout/update
using the "keoe" tag will not recover any such fixes. Should I
just tell you about any files I apply fixes to so you can update
your local checkout with them?
Mark
--
Mark Taylor Astronomical Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|