[Qgis-developer] Breaking API and merge of threading branch

[Tim Sutton]

Hi



On Thu, Aug 11, 2011 at 2:30 AM, Ramon Andinach <custard at westnet.com.au> wrote:
>
> On 10/08/2011, at 19:47 , Paolo Cavallini wrote:
>
>> Il 10/08/2011 13:30, Martin Dobias ha scritto:
>>
>>> We did not really plan to make a 1.8 release. I am a bit afraid that
>>> preparing another release might distract us from the road to 2.0.
>>
>> Agreed, I did not mean to have a formal release, just a quick snapshot before
>> breakage. I'm sure someone will find it useful.
>> All the best.
>
> I have but two questions for this thread, and it's more a user question than a developer question (and if I thought like the later, I'd probably be able to answer it myself).
>
> I recall discussion of a 1.7.1 backport type release, to cover the major bugs that weren't sorted in time for the 1.7 release.
> Is that still on?

Yes I will be announcing release plans for 1.7.1 probably over the weekend.

> If so, does this affect the possibility of a 1.7.1 release?
>

No. And we will do follow up 1.7.2 etc releases until 2.0 and maybe
beyond. But the number of things that we can reasonably backport to
the 1.7 branch will reduce as the two versions diverge.

> Just curiosity. 1.7 is doing a good job of what I need it for - so many thanks.

Nice to hear!

Regards

Tim

> -ramon.
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==============================================