[Gdal-dev] Radical OGR Update

[Frank Warmerdam]

Alessandro Amici wrote:
 > argh!
 >
 > what about a rapid 1.2.0 (with it's own cvs branch for fixes) and then start a
 > big restructure marked 2.0.0?

Andrey Kiselev wrote:
 > Those changes will take a time for implementing and especially for
 > testing. What about releasing GDAL 1.1.10 shortly?

Ben Discoe wrote:
 > I'd like to second that motion.  The best chance for making 1.2.0 a 'stable'
 > release is to put it out _before_ major changes.  Once the big changes
 > occur, we'll need to wait for a long time for broken things to be found and
 > resolved, before we can call it 'stable'.

Markus Neteler wrote:
 > Frank, please make a release before changing the API.

Folks,

OK, there seems to be a general agreement, that folks would prefer to have
a release now instead of in some indeterminate future after a bunch of
restructuring.  The release will be called 1.2.0 primarily because of the
change to use of libtool.  But also because my internal version macros won't
let me use a 10 for any of the release subcomponents. :-)

I will prepare a 1.2.0 alpha today.

Note that I hate branches, so I will want the 1.2.x series to settle down
now before proceeding to a 1.3.0 (or even 2.0.0) with the suggested OGR
changes.  That means giving things a few months for point releases.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent