[EMAIL PROTECTED] wrote:
The 2.2.x branch was started a little while ago.
It was marked as trunk for the longest time, from my perspective it
started the moment 2.1.0 was
released ;-)
So, I'm proposing making 2.2.x the 'official' stable branch.
That is the plan, we are waiting on a) someone to care (perhaps you)
and/or b) udig 1.1 (when I will
be the person caring).
I think this just requires getting an "official consensus", but I think
we just need to define what we mean by the 'official stable branch.'
Here's some ideas:
1. have a big "advertisement" on the geotools front page that announces
2.2.x as the 'official stable branch'
2. encourage (especially new) users to use the official stable branch
3. encourage users to report bugs against this version
4. encourage users to submit patches against this version
5. recommend people who need to make more substantive changes to use the
unstable (2.3) version and warn them of the implications.
One more:
6. Mark it stable aka 2.2.0 :-)
This means the 'official stable branch' isn't something we create and
then immediately forget about - its 'supported'.
Indeed the uDig 1.1 stable branch will based on this for at least 6
months to a year (aka what we
use to make money and feed ourselves).
The most controversial points will be "what changes are allowed to take
place on the stable branch"? Obviously things like changing the
feature model isn't in scope for the stable branch, but I'd still like
to see people able to add/fix things.
We do have stuff in our developers guide on this (working on a stable
branch page) .. from memory:
API changes - no
Functionality improvements - no
Functionality corrections - yes (i.e. when were were wrong about a
standard)
Additional Plug-ins - yes
Fun stuff,
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
