[Qgis-developer] Plans for next QGIS releases

[Tim Sutton]

Hi


On Tue, Feb 21, 2017 at 10:25 AM, Vincent Picavet (ml) <
vincent.ml at oslandia.com> wrote:

> Hi Paolo,
>
> Please excuse me if I missed something, but I am quite surprised, not by
> the decisions themselves, but the process of these decisions.
>
> I have seen no call for meeting, no message to the list to gather
> advices, no mention to voting members neither of this IRC meeting
> happening.
> The topic is really important and has deep consequences for all of our
> users, funders, developers. The least we can do is ask them for their
> advice and feedback. This kind of autocratic top-bottom decisions is
> definitely not the way I would expect the QGIS community to behave.
>
> Sorry for the rant, and again I may have missed something ( but I
> re-checked all emails from PSC, dev and users ML, my #qgis logs, and saw
> nothing). Let's keep the community involved in decision processes and
> take care about how we communicate together, please.
>


​Just to confirm what Paolo said, the issue was raised by Paolo at our PSC
meeting 2 months ago (all meeting minutes are publicly available at
https://github.com/qgis/qgis/wiki#psc-meeting-minutes), and the suggested
approach was:

* form a small group of core developers to come up with a viable proposal
for 3.x plans - Done
* present the proposal to the mailing list for further discussion ​- Done
* based on feedback from the discussion publicise the plan further on the
QGIS blog - (still to be done)

There are many viable responses including:

* agreeing with the proposal here on the mailing list
* disagreeing and providing substantive reasons why and a clear alternative
* proposing that the issue goes to a voting member vote if there are
conflicting alternatives

I think this is all pretty clear and transparent - and I think it is better
to start the discussion with a viable solution rather than an extremely
broad and open ended question like 'how shall we handle the release?' as a
starting point -  which is going to lead to a jumbled flow of hard to
manage proposals.

So to summarize, we are doing out best to keep all communications in the
project open and transparent, if there are substantive suggestions about
how to improve things, just share them here and we will do our best to
incorporate them.


Regards

Tim






>
> Vincent
>
> On 20/02/2017 11:17, Paolo Cavallini wrote:
> > Hi all,
> > during a fast and productive IRC meeting today we have come out with a
> > proposal for the management of current and future versions of QGIS:
> >
> > * retire 2.14 in June 2017
> > * 2.18 becomes LTR from June 2017 to 2018
> > * 3.0 feature freeze in July 2017
> > * release 3.0 in Sept 2017
> > * release 3.2 as next LTR in release 3.0 + 4 Months (eta June 2018).
> >
> > Of course we know that some of you will have different preferences and
> > constraints, but we believe this is the best compromise we can reach
> > now. Please let us know if you have strong opposition to this, or good
> > argument to change. Nothing is carved in stone, but it will be good to
> > give our users and devs a perspective on what they can expect.
> >
> > All the best.
> >
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
------------------------------------------------------------------------------------------
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170221/a005599a/attachment-0001.html>