[gdal-dev] GDAL 2.0 release plans

Ari Jolma ari.jolma at gmail.com
Thu Apr 30 02:12:36 PDT 2015


29.04.2015, 21:40, Even Rouault kirjoitti:
> Hi,
>
> I wanted to have an update from other developers to know where there are with
> respect to their planned schedule.
> I had noted that :
> - Dmitriy wanted to integrate his work on metadata support for various
> satellite imagery. I have reviewed a preliminary version of it.
> - Ari has ongoing work on Perl. I've seen a few commits passed.
> - Pirmin intended to add curve support in Interlis. Haven't seen yet any
> commit.
>
> Are you still in track to finalize those works in the following days ? Would
> adding the week-end help to have that in Beta1 ? I especially think to
> Dmitriy's work who is quite substantial, and perhaps Perl changes if there are
> still breaking change to come. Interlis specfic changes might arrive after
> Beta1 I think.

There is *a lot* for me still to go through (mainly with writing tests 
and thus seeing if the interface is ok). But maybe the only big breaking 
change thing to do would be to harmonize the constructors.

Swig adds the standard Perl "new" but I've marked that in many cases 
deprecated since I want to use for example human readable strings and 
not integer constants (for example "Point" instead of 
$Geo::OGR::wkbPoint). This has led to a set of "create" constructors. In 
version 2 all the constructors should/could be called "new". Now I know 
how this can be done using a "shadow" feature of Swig.

I can do that today and then I'd be ok for 2.0 beta.

Ari

>
> Even
>
>
>> Hi,
>>
>> Some time ago, I mentionned my proposal of issuing a first GDAL 2.0 beta
>> version for the end of this month (April 30th). Are there objections to
>> sticking with that plan ? Does someone need a bit more time to finish an
>> ongoing work ?
>>
>> And if things go well with this beta (and potentially other beta(s)
>> needed), we could try a release candidate for end of May. One month of
>> beta phase might seem a bit short, but I'm not sure extending the beta
>> testing period more will bring significant additional feedback (and things
>> tend to slip, so better aim for a tight schedule). Thoughts ?
>> Anyone using GDAL intensively and/or interesting in 2.0 should already
>> track trunk closely ;-)
>>
>> I can wear the hat of 2.0 release manager, but I'm happy to let it to any
>> other volunteer.
>>
>> Best regards,
>>
>> Even



More information about the gdal-dev mailing list