[QGIS-Developer] [Qgis-psc] Feature freeze: Paid developer activities for QGIS 3.0

[Andreas Neumann]

Hi all, 

I agree with Régis. It would be useful to have the layouts instead of
the old composers in QGIS 3. It would be better than the other
alternatives, even if it would mean a further delay of the QGIS 3
release. 

We just have to think about the consequences. Personally, I would
propose to delay the QGIS 3 release again a bit, e.g. release later in
December, just before Christmas - because I do think that the bug fixing
period, as it is scheduled now is too short. 

Just my personal opinion. I would prefer to have a quick decision here. 

Andreas 

On 2017-11-03 09:38, Régis Haubourg wrote:

> Hi all,  
> 
> 2017-11-03 8:52 GMT+01:00 Nyall Dawson <nyall.dawson at gmail.com>:
> 
>> On 2 November 2017 at 22:08, Andreas Neumann <a.neumann at carto.net> wrote:
>> [...]
>> But the alternatives are:
>> 
>> 1. Ship with composer, and keep exposing composer API. We'll be stuck
>> with composer for the life of 2.x, and when layouts lands in 3.2 we'll
>> end up with duplicate buttons for "new composer"/"new layout", or some
>> option to switch the print backend from composer/layouts. Ouch! Not to
>> mention that we'll be forced to carry around and maintain thousands of
>> lines of old code for the next x years.
>> 
>> 2. Ship with composer in 3.0, but remove from bindings (e.g.
>> https://github.com/qgis/QGIS/pull/5486 [1]). Then after thaw I can merge
>> layouts and drop all the composer code. Downside is no ability to
>> script or have composer based plugins in 3.0. Upside is layouts lands
>> with the new clean api in 3.2, and we can have a clean-start then.
>> Another upside is the additional full cycle of testing for layouts
>> which means that when it's available to users in 3.2 it should be
>> rock-solid.
>> 
>> That's me laying out all the options as I see them. I'm honestly happy
>> to abide by whatever decision the release manager/PSC makes here. I
>> don't envy their position in making this call (sorry!)
> 
> Is there no option 3 "drop composer totally and merge layouts " ? It was the very first need that started QGIS3 project IIRC.  
> 
> On our side, we will be severely impacted for short time project if we drop composer, but I think the mid term option with mixed composer and layout in QGIS will cost al lot more to all of us. Users won't understand having both, and not having python bindings to layout in 3.0 will be a no go for deploying applications. So that would be the same as tagging 3.0 as a release candidate version, which is not the path we chose.  
> 
> Regards 
> Régis

 

Links:
------
[1] https://github.com/qgis/QGIS/pull/5486
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20171103/5f5c7b86/attachment.html>