[Qgis-developer] Four month cycle too fast

[Andreas Neumann]

Hi,

I'd like to add to the discussion that there will be more organizations
investing in bug-fixing in the future. Yesterday, a Swiss canton told me
that they will invest 5000 CHF each year in QA/bugfixing in the future.
I am pretty sure that more organizations will follow.

This means that more developers will be able to work on paid bugfixing
(e.g. 3-4 devs working each 1-2 weeks for each release). I think that
this will help a lot to raise the quality.

But it is important that we will provide bug-fix releases and that there
is a reasonable time available for testing. The short releases do not
help at all for organizations - because each new release introduces more
and different bugs.

We users need bug-free software more than a predictable release date. We
don't need QGIS at an exact specific time. But we cannot accept that
some features are broken that are key to our work.

Andreas


Am 19.06.2014 09:18, schrieb Jürgen E. Fischer:
> Hi Andreas,
> 
> On Thu, 19. Jun 2014 at 06:34:17 +0000, Andreas Neumann wrote:
>> I would propose to try a six month release cycle with two months feature
>> freeze for testing (see also my previous mail about a request for more time
>> for testing/bug fixing). Even a yearly release cycle would be fine, if there
>> could be a bug-fix release.
> 
> But the short release cycle is there to avoid the need of bugfix releases -
> because we learned in the past that we don't have enough (interested and
> skilled) people to maintain the backports and we also miss a scheme to test
> them before we apply them.
> 
> And IMHO a year too long to wait for new features in a release anyway.
> 
> Four months is a compromise between avoiding bugfix releases and getting new
> features released.
> 
> 
> Jürgen
>