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

[Nyall Dawson]

On 3 November 2017 at 18:38, Régis Haubourg <regis.haubourg at gmail.com> 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). 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.

Yes - that's definitely an option! 1 and 2 were "alternatives" to doing that.

Nyall