[Qgis-psc] The inevitable question: extending freeze for 3.0?
Nathan Woodrow
madmanwoo at gmail.com
Sun Jul 9 16:45:45 PDT 2017
Hey,
Yes please that would be super handy to have some extra time. Profile work
is getting close and should be in this week at this rate.
Regards,
Nathan
On Mon, Jul 10, 2017 at 8:10 AM, Tim Sutton <tim at kartoza.com> wrote:
> Hi
>
>
> +1 from me too for pushing the date back as needed - I'd rather we have
> all the key API changes in place since we are setting the foundation for
> the next ~5 years here....
>
> Thanks!
>
> Regards
>
> Tim
>
> On Sun, Jul 9, 2017 at 3:44 PM, Andreas Neumann <a.neumann at carto.net>
> wrote:
>
>> +1 for pushing the feature freeze back from Mid August for at least one
>> more month. End of September would be a reasonable date.
>>
>> I am also in favour of having more than one month for bug fixing before
>> we release 3.0
>>
>> There are so many changes that went into the 3.x (master) branch and
>> there will be more than usual bugs. So I am afraid that one month of bug
>> fixing is not enough to get a reasonably stable and useful release.
>>
>> Andreas
>>
>>
>>
>> On 07.07.2017 14:56, Nyall Dawson wrote:
>>
>>> Hi PSC,
>>>
>>> There's a lot of major work still outstanding which would be good to
>>> land in 3.0, and which is actively being worked on by developers. This
>>> includes my layout work, the ongoing processing changes (although
>>> these are nearly complete - more on that later), Lutra's 3d work, the
>>> recently funded remaining server improvements, and Nathan's
>>> configuration/profiles work (+ ideally the ongoing metadata work, if
>>> someone steps up to fund the remaining work packages).
>>>
>>> Given that the freeze is coming up quickly, I'd like to raise the
>>> discussion now about whether we could/should push this back by a
>>> month.
>>>
>>> My personal situation is that while I should be able to complete the
>>> layout work and the processing changes by the current freeze, an extra
>>> month would allow me time to really make these improvements shine
>>> (especially processing would benefit from an extra month to port all
>>> the existing algorithms... but that's another discussion I'll raise
>>> soon).
>>>
>>> Is this possible? A good idea? A bad idea? Desired by anyone else but me?
>>>
>>> Nyall
>>> _______________________________________________
>>> Qgis-psc mailing list
>>> Qgis-psc at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>
>>
>> _______________________________________________
>> Qgis-psc mailing list
>> Qgis-psc at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>
>
>
>
> --
> ------------------------------------------------------------
> ------------------------------
>
>
> Tim Sutton
> Visit http://kartoza.com to find out about open source:
> * Desktop GIS programming services
> * Geospatial web development
> * GIS Training
> * Consulting Services
> Skype: timlinux Irc: timlinux on #qgis at freenode.net
> Tim is a member of the QGIS Project Steering Committee
> ------------------------------------------------------------
> -------------------------------
> Kartoza is a merger between Linfiniti and Afrispatial
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20170710/307af68e/attachment.html>
More information about the Qgis-psc
mailing list