Martin,
we are obviously late on the initial schedule... We aim at issuing
1.7.0-beta2 very soon, but as it is not issued yet, it still gives you
the opportunity to commit the driver if you're confident enough it won't
cause too much build problems. If so, please commit the code very soon.
Otherwise the next timeframe will likely be after the creation of the
1.7 maintenance branch, which would occur in, well, 2 weeks ?, after we
have issued the release candidates. At that point, trunk will then be
considered as 1.8dev and proper again for adding new features. (For the
period after beta2 and before 1.7 maintenance branch creation, I think
the policy is "feature freeze - fix only"). The 1.7.0 version should be
officialy released before end of January if everything goes well.
Best regards,
Even
Hi all,
2009/12/26 Martin Landa <landa.mar...@gmail.com>:
2009/12/26 Even Rouault <even.roua...@mines-paris.org>:
As 1.7.0 release should happen soon, the top priority is to be careful not
to break GDAL building. You can have a look at the various slavebots at
http://buildbot.osgeo.org:8500/waterfall to check that everything is OK.
probably I should wait for releasing 1.7.0 [1] and after that add new
VFK driver. What do you think?
I would like to ask you about status of 1.7 [1] or better to say if
it's better to include VFK driver now or later...
Thanks in advance, Martin
[1] http://trac.osgeo.org/gdal/wiki/ReleasePlan17
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
