Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Jeremy Palmer
I've just been testing GDAL/OGR 1.11.0 and the MBTiles driver does not seem to be reading transparency information. Not sure if this is new to 1.11.0 or was an issue there before. Ticket here: http://trac.osgeo.org/gdal/ticket/5439 Cheers, Jeremy This message contains information, which may be

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Even Rouault
> Code reviews would be another way to prevent accidental > segfaults, but we might not have enough people with enough time for that, > and some people might not want it. I personally love when someone reviews > my code. Code reviews are of course good for quality. I think any GDAL committer shoul

[gdal-dev] Formalizing realease procedure [was Re: GDAL/OGR 1.11.0 Release Candidate 1 available for testing]

2014-04-17 Thread Even Rouault
Le jeudi 17 avril 2014 17:03:50, Wolf Bergenheim a écrit : > Hi Daniel, > > I agree with your idea about formalizing, and do indeed feel sorry for > adding to Even's workload. I think it's a good thing to talk about, > especially now, for obvious reasons. Making new GDAL releases should be > made

Re: [gdal-dev] Source code for ogr2ogr --version

2014-04-17 Thread Mateusz Łoskot
On 17 April 2014 21:26, David Tran wrote: > Hi to everyone > > I compiled gdal 1.10.1 and now I want to show ogr2ogr --version with my > library in my ide console. How do I do that with C or C++? Use GDALVersionInfo function, see http://www.gdal.org/gdal_8h.html Best regards, -- Mateusz Łoskot

[gdal-dev] Source code for ogr2ogr --version

2014-04-17 Thread David Tran
Hi to everyone I compiled gdal 1.10.1 and now I want to show ogr2ogr --version with my library in my ide console. How do I do that with C or C++? Thanks in advance. David ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mail

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Even Rouault
> Ok, no need for it then. Do you want me to roll my changes back from the > 1.11 branch or apply my patch to it? You can apply your patch on 1.11 as well. It will be stacked for a potential new RC, or a 1.11.1 release. I'm still ambivalent about regnerating a new RC, just to incorporate the spat

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Wolf Bergenheim
On Thu, Apr 17, 2014 at 3:01 PM, Even Rouault wrote: > > I suppose, but the problem is that without it the whole thing becomes > > useless for large datasets (> 100k features) due to GME restrictions. I > > just thought that it would be good to have a GME driver that works on > those > > large tab

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Wolf Bergenheim
Hi Daniel, I agree with your idea about formalizing, and do indeed feel sorry for adding to Even's workload. I think it's a good thing to talk about, especially now, for obvious reasons. Making new GDAL releases should be made as easy as possible, and I think that a more formal structure, like the

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Daniel Morissette
Hi Wolf, Once again my mail was aimed at all of us committers and not just you specifically. Your contributions (like everyone else's) are much welcome and I would not want to discourage anyone from contributing. FWIW I don't think there was ever a formal code freeze call for GDAL, so you did

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Wolf Bergenheim
Yeah, I should not have tried to push this so late yesterday. For that I'm sorry, and I'm fixing it now. I can only apologize. Daniel, you bring up a good point. A more formal release process might be in order, we are maybe starting to reach critical mass in developers here, or else it's just me m

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Daniel Morissette
On 14-04-17 9:01 AM, Even Rouault wrote: The problem is that at some point we must take a snapshot and say "hey, this is GDAL 1.11, the latest and greatest, use it please". I think it is OK if new drivers are still a bit experimental. Reviewing the commit, I think that it has at least one issue

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Daniel Morissette
On 14-04-17 9:56 AM, Daniel Morissette wrote: For reference, MapServer RFC34 documents the release process: http://msgsoc.mapgears.com/html/en/development/rfc/ms-rfc-34.html OOppss. The URL above points to a mirror of the site. Here is the official URL to RFC 34: http://mapserver.org/devel

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Even Rouault
Selon Wolf Bergenheim : > On Thu, Apr 17, 2014 at 9:56 AM, Even Rouault > wrote: > > > Selon Wolf Bergenheim : > > > > > I just added a critical fix gor the GME driver that I'd like to get in to > > > 1.11, so I merged it to the 1.11 branch. Soo technically this might > > require > > > a new RC, s

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Wolf Bergenheim
On Thu, Apr 17, 2014 at 9:56 AM, Even Rouault wrote: > Selon Wolf Bergenheim : > > > I just added a critical fix gor the GME driver that I'd like to get in to > > 1.11, so I merged it to the 1.11 branch. Soo technically this might > require > > a new RC, sorry for that! > > I'd like to kindly remi

Re: [gdal-dev] GDAL/OGR 1.11.0 Release Candidate 1 available for testing

2014-04-17 Thread Even Rouault
Selon Wolf Bergenheim : > I just added a critical fix gor the GME driver that I'd like to get in to > 1.11, so I merged it to the 1.11 branch. Soo technically this might require > a new RC, sorry for that! I'd like to kindly remind to GDAL committers that any commit worth to go to a branch must b