[Qgis-developer] Merging of incompatible changes

Radim Blazek radim.blazek at gmail.com
Wed Oct 24 01:20:00 PDT 2012


On Tue, Oct 23, 2012 at 10:58 PM, Pirmin Kalberer <pi_ml at sourcepole.com> wrote:
> Hi Martin,
>
> Am Montag, 22. Oktober 2012, 21.17:20 schrieb Martin Dobias:
>>
>> recently I have been brewing some backwards incompatible API changes
>> that will 1) enable introduction of threading, 2) simplify API for
>> developers. I would like to merge the changes soon to master branch in
>> order not to drift too much from master.
>
> -1 from me.
> This is against the release plan we agreed on the hackfest.
>
> IMHO, current master can be a great 2.0 release with many new features in a
> few months.
> Your additions are the begin of the next level - an even greater 3.0 release.

So what was the conclusion about threading? I had to leave HF during
the discussion but my impression was that threading was marked as
important and it should go to 2.0. If Martin is finally willing to
merge threading we should support him. The threading branch (the
knowledge) could also be lost during the years until the 3.0 release.

Is there the 2.0 changes list written on flip chart on HF somewhere on
wiki? If not, I'll start one. Is there a photo?

Radim

> So I would strongly prefer to have these changes in a "plugin-ng"-branch
> instead of starting a "frozen" 1.9 branch.
>
> Regards
> Pirmin
>
> --
> Pirmin Kalberer
> Sourcepole  -  Linux & Open Source Solutions
> http://www.sourcepole.com
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer


More information about the Qgis-developer mailing list