[EMAIL PROTECTED] wrote:
I'm quite worried that if geotools doesn't have a supported stable
branch that we're going to get ourselves in trouble. I also think that
having official stability will encourage new users, bug reports, bug
fixes, and documentation. We really need that!
Indeed, and thanks for the encouragement Dave. I think everyone will be
happier once we settle on a course
of action ;-) And please be patient with us, remember geotools is really
only on its third real release here,
we are all learning and figuring it out as we go along.
Put another way:
- 2.0.0 showed a release was possible (after 6 years), it is too bad
that a lot of volunteers were just helping out until this happened ;-)
(yeah everyone!)
- 2.1.0 taught us how to do our first major API shift
(CoordinateReferenceSystem) and how scary that was (and costly in terms
of developer trust). And frankly my trust.
- 2.1.1 showed that a stable release was possible, one that was
maintained (yeah Dave)
- 2.2.0 showed us a much better way of development where short term (two
week branches) were merged in to create milestones resulting in a trunk
that could be released at any point (yeah everyone)
- 2.3.M0 showed us how a major api shift could be done using the branch
and merge idea (yeah Justin)
- 2.3.M1 is stretching everything to it limit as we revise the heart of
geotools (hold on Justin)
- 2.4.x is going to show us if the long term branch idea will work
(coverage will be out for over a year at that point!)
Cheers,
Jody
-------------------------------------------------------
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&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
