Le jeudi 03 novembre 2011 22:33:38, Mateusz Łoskot a écrit : > On 3 November 2011 21:26, Kyle Shannon <kshan...@gcs-research.com> wrote: > > I believe that is on the 2.0 changes list, or something along those > > lines. See: > > > > http://trac.osgeo.org/gdal/wiki/GDAL20Changes > > > > under House Keeping issues > > Great news! > > Frank, Even, > Can I set http://trac.osgeo.org/gdal/ticket/3435 with 2.0 milestone?
There's was no 2.0 milestone created yet in Trac, so I've just created it. By the way, it's not clear (to me) if 2.0 will be the next version or if there will be a 1.10 before. I think that the ideas mentionned in GDAL20Changes are only brainstorming material for now that anyone can contribute to, but they should not be considered as officially approved until they will be seriously discussed. I can imagine that feedback, not only from developers, but also for the large crowd of users will be needed, so that each breaking change is pondered. The main issue with 2.0 is that it should be the opportunity to do most breaking changes that can be anticipated for the next few years. But that also means that people that can contribute to it will need to have enough time/motivation/funding at the time that the works start, so that it ends up to be releasable in a reasonable amount of time (I'm just thinking to the libtiff 4.0 situation...). There's also the risk of a fork of the community between users strongly attached to the old 1.X series (and potentially wishing improvements in the frame of this series) and users who will join the 2.X train. I'm thinking to the Python 2 vs Python 3 situation here. Looking at http://trac.osgeo.org/gdal/wiki/SoftwareUsingGdal makes you feel how many projects can be affected by the decisions that will be taken. And that's just the verbose crowd, not to mention the crowd of silent users that is likely much larger... > > Best regards, _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
