[Qgis-developer] Merging of incompatible changes

[Marco Hugentobler]

Hi defs

Yes, the decision was that multithreading branch should be in 2.0. 
Personally, I'm in favor of merging it as soon as possible (to give the 
dev team enough time to get used to the new classes and to handle 
possible side effects). Martin, is your planned merge already the full 
threading branch merge or a part of it?

Pathon changes: I don't have a strong opinion here, but most people on 
the list seem to be in favor of them ( they are not afraid to adapt 
their plugins for 2.0).

 >We also decided that the geometry refactoring (for arcs, splines, 
z-values, m-values, multitype >geometries, etc.) should be done after 
QGIS 2.0. I am not sure if this would again mean API breaks ...

I think that can wait until version 3...

Regards,
Marco

On 24.10.2012 16:13, Andreas Neumann wrote:
> Hi Pirmin and others,
>
> Tim should correct me - but as far as I remember we said that 
> threading support is one of the major things we want to see in QGIS 
> 2.0 (along with raster redesign, atlas printing and others). But none 
> of us were sure in what timeframe Martin can work on it and when it 
> will be finished. Therefore we decided not to make it a blocker.
>
> We also decided that the geometry refactoring (for arcs, splines, 
> z-values, m-values, multitype geometries, etc.) should be done after 
> QGIS 2.0. I am not sure if this would again mean API breaks ...
>
> So I am against postponing the multithreading work and I had the 
> impression that this was the conclusion of others as well.
>
> Andreas
>
> On Tue, 23 Oct 2012 22:58:25 +0200, Pirmin Kalberer 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 I would strongly prefer to have these changes in a "plugin-ng"-branch
>> instead of starting a "frozen" 1.9 branch.
>>
>> Regards
>> Pirmin
>


-- 
Dr. Marco Hugentobler
Sourcepole -  Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
marco.hugentobler at sourcepole.ch http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee