[Qgis-developer] Four month cycle too fast

[Nathan Woodrow]

>
>
> 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
>

Exactly. There is no point having a release if people can't use it.  It
will leave a bad taste, especially if it's rolled out to organizations.

Nothing will ever be perfect but any blockers (provided that they are) need
to be fixed before release. There was one the other day where you couldn't
add a new column which is pretty major.

- Nathan


> 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
> >
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140619/d0a7cbd9/attachment.html>