[EMAIL PROTECTED] a écrit :
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.
I would like to add one more criteria. Currently, the 2.2 branch depends on GeoAPI 2.0 (the latest
stable version). I would like that it stay like that. I mean, the 2.2 branch should not depends on
any kind of "geoapi-pending-xxx" version. This condition would exclude current Feature work, since
they depend on the ongoing work in the GeoAPI pending directory. The GeoAPI dependency should stay
frozen to 2.0.
Martin.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
