Good Evening Harald,
There is one added wrinkle - one of the reasons trunk is unstable is
because we are finding and fixing bugs
in the GeoTools (and sometimes GeoAPI library). In the past I have been
able to make monthly releases
of this library ... and that would be a perfect time to "tag" uDig trunk
(ie when they can
actually name the version of GeoTools they depend on - rather than just
getting the "latest snapshot").
I am going to (for a customer) go back and tag a version of uDig trunk
that was building against the
GeoTools 2.5.x stream. The main difference between GeoTools 2.5.x and
GeoTools 2.6.x right now
is improvements to the SLDParser done so uDig could work with
RasterSymbolizers successfully.
To be clear; just because we tag it does not mean it will be something
that can be built later; we need
to also mark down the which SNAPSHOT jars were used for the tag; this
can be done by updating
a couple of entries in the copy.properties file in
net.refractions.udig.libs.
Cheers,
Jody
Wellmann, Harald wrote:
Ok, I'd better move to the trunk then...
So if the trunk and the 1.1.x branch have grown so far apart, wouldn't
it be useful to create a tag from the trunk once a month or so to mark a
stable build? From the messages on this list, I get the impression that
trunk builds are broken once in a while, so working on head revision is
probably not a good idea when you are trying to develop a uDig add-on,
and not uDig itself.
Incidentally, I always assumed that the "RC" in "1.1-RC14" stands for
"Release Candidate", so I was wondering when the magic 1.1.0 release
would finally arrive.
Now I get the impression that the 1.1.x branch is simply your stable
branch and that you provide bugfix releases in regular intervals.
Maybe it's just a matter of personal taste and habit, but I think it
would be more intuitive to call these stable releases 1.1.14, 1.1.15
etc. and to start creating release candidate tags 1.2RC1, 1.2RC2, ...
from the trunk until the trunk gets stable enough to cut a 1.2.0 release
and a 1.2.x release branch while the trunk moves ahead towards 1.3.
Is there a particular target in terms of functionality or timeline for a
release 1.2?
Regards,
Harald
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
