[Qgis-psc] PROPOSAL: change how we manage the 3.0 release process

[Régis Haubourg]

Hi Tim,

 I agree QGIS 3.0 is sort of an exception, we have a lot a major
refactoring that need to land in it.

However, I think we should keep fixed date releases within major version
lifecycle, and in the same time improve our feature roadmap planning. Let
me explain why.

 - Release when ready would imply that we all can announce in advance what
feature we will bring in each version. By now, we are not structured for
that I think.
 - Fixed date releases are very good for users, developpers and funders to
plan work and anticipate. It also allows to avoid those huge delays we have
currently in QGIS3, with too much untested nex features. Release often is
the key for real user testing.

So my vote would be to allow unfixed schedule for major releases, but with
a better project management of critical features and API break we need in
it, and keep fixed date minor releases.

My two cents,
Regards
Régis

2017-11-06 10:43 GMT+01:00 Tim Sutton <tim at kartoza.com>:

> Hi All
>
> We have our PSC meeting tonight and I have added an agenda item about
> feature freeze exceptions. I will respond immediately after the meeting
> with any decision that has been reached, or if we are not able to reach a
> consensus I will put it to a general members vote.
>
> As Jürgen is release manager, I would prefer that we have his agreement
> and buy-in (he has already stated a contrary opinion to lifting the freeze
> - http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-
> Feature-freeze-Paid-developer-activities-for-QGIS-3-0-
> tp5340245p5340300.html).
>
> Probably more accurately I should state that Jürgen already agreed in
> Girona to go to a fixed release schedule in preference to a  ‘when it is
> ready’ schedule as was originally planned.
>
> At the risk of severely irritating Jürgen (sorry!), why don’t we move back
> to a ‘release when ready’ approach which might also have the happy
> by-product of being less work for him since he only needs to deal with the
> process once when the release is deemed ready.
>
> One simple mechanism we could do is have a rolling voting member’s vote
> (e.g. at then end of each month) with a simple question “shall we freeze”?
> Once we have quorum on that vote, we go ahead and freeze and Jürgen can
> pretty much ignore 3.x in his release planning until that vote passes. We
> also have the by-product that we cannot tell our users / customers / fans
> when the release will be ready but by-and-large I think the outcome will be
> better since we all will be dancing to the same tune and we can make sure
> 3.0 has everything in it that we think it should have without compromises.
>
> I also propose that the paid bug fixing should commence now already
> regardless of when the freeze will actually happen.
>
>
> Our PSC meeting is at 8pm CET (sorry thats an awful time for you Nyall)
> and anybody is always welcome to sit in the call if you wish you raise your
> concerns in person (or send me any notes for things that you would like
> raised on your behalf).
>
>
> Regards
>
> Tim
>
> —
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Project chair:* QGIS.org
>
> 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
>
> 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/20171106/5bcbd038/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KartozaNewLogoThumbnail.jpg
Type: image/jpeg
Size: 6122 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20171106/5bcbd038/attachment.jpg>