Re: [gdal-dev] GDAL/OGR 2.0 Notes

2010-09-23 Thread Frank Warmerdam
Ivan Lucena wrote: We can always have 1.10 and 1.11 etc. That would not be uncommon (there is for example Perl 5.10 as we're waiting for Perl 6). However, I'm for I like that. Folks, Well, I hate two digit releases, and they confuse the versioning in stuff like OSGeo4W. Not a compelling r

Re: [gdal-dev] GDAL/OGR 2.0 Notes

2010-09-23 Thread Ivan Lucena
> ---Original Message--- > From: Ari Jolma > To: gdal-dev@lists.osgeo.org > Subject: Re: [gdal-dev] GDAL/OGR 2.0 Notes > Sent: Sep 23 '10 09:04 > > On 09/22/2010 09:52 PM, Frank Warmerdam wrote: > > Folks, > > > > In IRC I was jus

Re: [gdal-dev] GDAL/OGR 2.0 Notes

2010-09-23 Thread Ari Jolma
On 09/22/2010 09:52 PM, Frank Warmerdam wrote: Folks, In IRC I was just mentioning to Howard that we might want to drop use of CPL_STDCALL in the GDAL API if a 2.0 release ever occurs. It seemed to me that such ideas ought to be kept track of so off the "Developer" section of the Trac wiki I

Re: [gdal-dev] GDAL/OGR 2.0 Notes

2010-09-22 Thread Doug_Newcomb
>As we are running out of 1.x numbers (1.8.0 hopfully coming out soon), I'm >thinking about a 2.0 release for something like the fall of 2012 - just in >time for the world to end. That should simplify keeping track of the EPSG codes... Doug Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 1

[gdal-dev] GDAL/OGR 2.0 Notes

2010-09-22 Thread Frank Warmerdam
Folks, In IRC I was just mentioning to Howard that we might want to drop use of CPL_STDCALL in the GDAL API if a 2.0 release ever occurs. It seemed to me that such ideas ought to be kept track of so off the "Developer" section of the Trac wiki I have created a page for this and pre-populated it