[Qgis-developer] Roadmap for 2.2

[Nathan Woodrow]

+1 from me for this kind of release schedule.  Knowing that there is a
release coming in X months puts users minds at ease and lets devs focus on
what they can do and when, and not rushing things last minute.

Waiting for features is just asking for the "we will just wait for this,
and that, and this, and maybe this"

I think we are in a good place now to be making faster releases.

- Nathan


On Tue, Nov 5, 2013 at 9:24 PM, Alexander Bruy <alexander.bruy at gmail.com>wrote:

> Hi,
>
> I agree with Jürgen and Marco, fixed release schedule is better than
> waiting for features. Also having month for testing should be enough
> for finding most major bugs/regressions, so releases will be more
> stable and robust.
>
>
> 2013/11/5 Jürgen E. <jef at norbit.de>:
> > Hi Paolo,
> >
> > On Mon, 04. Nov 2013 at 20:01:02 +0100, Paolo Cavallini wrote:
> >> wouldn't it a good time to do it now then? :)
> >
> > My/The plan is to have a fixed release every four months.
> >
> > So if we started with the last release the next release would be in
> january,
> > then may and september and so forth.
> >
> > What I didn't expect was that the 2.0 release would take this long for
> me -
> > mostly not actual QGIS problems, but stuff in OSGeo4W.   So I'm still
> busy
> > catching up with my other duties and got behind with the release plan.
> >
> > Anyway, the 4 months would be split into three months of development and
> one
> > month for testing, bugfixing, translating and release preparations in a
> freeze
> > period.
> >
> > So if everyone knows beforehand when the next release will happen, new
> things
> > can be scheduled to be introduced into a certain release slot.  Things
> that
> > take more than one slot, should go into a seperate branch and merged
> when they
> > are ready.
> >
> > So the release should just be determined just by time and be not be tied
> to
> > some desireable feature set/level of improvement or some other thing
> that might
> > or might not have happened at a given point in time and delay the next
> release
> > for an unknown amount of time.
> >
> > Does jan/may/sep sound preferable?  feb/jun/oct or mar/jul/nov or
> apr/aug/dec
> > any better?  Any preference on the week or weekday such a release should
> happen
> > (eg. 3rd friday of the month)?
> >
> > The idea also was to thereby reduce the need to stable releases and not
> to do
> > any. As I originally thought, we didn't have the manpower to maintain
> them.  As
> > we already established two times and I'm still doubtful that we're now.
> > So this doesn't cover stable releases at all.
> >
> > Opinions?
> >
> >
> > Jürgen
> >
> > --
> > Jürgen E. Fischer         norBIT GmbH               Tel.
> +49-4931-918175-31
> > Dipl.-Inf. (FH)           Rheinstraße 13            Fax.
> +49-4931-918175-50
> > Software Engineer         D-26506 Norden
> http://www.norbit.de
> > QGIS PSC member (RM)                                   IRC: jef on
> FreeNode
> >
> > --
> > norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
> > Rheinstrasse 13, 26506 Norden
> > GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502
> >
> > _______________________________________________
> > Qgis-developer mailing list
> > Qgis-developer at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alexander Bruy
> _______________________________________________
> 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/20131105/a11f3723/attachment.html>