<br><div class="gmail_quote">On Wed, Jun 10, 2009 at 12:29 PM, Even Rouault <span dir="ltr"><<a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
1.7 release date hasn't been decided yet. There is no precise criterion to<br>
determine when it happens : it depends mainly on when RFC or major work<br>
planned by developers have been implemented. But if you look at the release<br>
date of previous "major" versions (1.6.0 ~ 04-Dec-2008, 1.5.0 ~ 20-Dec-2007,<br>
1.4.0 ~ 5-Jan-2007), you could expect 1.7.0 for the end of 2009.<br>
</blockquote><div><br>Good to know. <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Depending on the bug fix (which one are you refering to ? ticket number, SVN<br>
revision), it could be considered to be backported into the next maintenance<br>
version of the 1.6.x branch. But 1.6.1 has been released just a few weeks<br>
ago, so 1.6.2 won't likely be released before a few months.<br>
<br>
</blockquote></div><br>I'm looking at ticket #2989. See: <a href="http://trac.osgeo.org/gdal/ticket/2989">http://trac.osgeo.org/gdal/ticket/2989</a><br><br>I'll likely end up creating a patch for my gentoo ebuild unless this gets backported into a 1.6.2 release. It's tough to deal with some of the new, large GeoEye-1 scenes without this fix. <br>
<br>Thanks,<br>Matt<br>