<div dir="ltr"><p dir="ltr">I'm not sure I really like the "just make new releases and avoid bug fixe releases" kind of thinking. There are some places that can't roll out a whole new release due to possible bugs from major new features, and given how fast we move this can cause some real issues. </p>
<p>We don't even have to bug fix until next release just do it for a short (1 month) period after the release, so you're dev cycle is like this:</p><p>6 month dev (including ~1 month freeze) -> release -> 1 month post release freeze -> release a bug fix release if needed -> move on.</p>
<p>This means any bugs that might come up can be fixed, and we patch then we move on. There is really no need to make 2.x.5 releases, just one would normally be enough.</p><p>I think the main thing is keeping the bug fix patches small so you don't affect to much code and is easier to spot where there might be issues.</p>
<p>Packaging for each platform is up to that maintainer but that should be automated as much as possible really otherwise making releases is too hard. </p><p>- Nathan</p>
<div class="gmail_quote">On Jun 19, 2014 7:18 PM, "Jürgen E." <<a href="mailto:jef@norbit.de" target="_blank">jef@norbit.de</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Andreas,<br>
<br>
On Thu, 19. Jun 2014 at 06:34:17 +0000, Andreas Neumann wrote:<br>
> I would propose to try a six month release cycle with two months feature<br>
> freeze for testing (see also my previous mail about a request for more time<br>
> for testing/bug fixing). Even a yearly release cycle would be fine, if there<br>
> could be a bug-fix release.<br>
<br>
But the short release cycle is there to avoid the need of bugfix releases -<br>
because we learned in the past that we don't have enough (interested and<br>
skilled) people to maintain the backports and we also miss a scheme to test<br>
them before we apply them.<br>
<br>
And IMHO a year too long to wait for new features in a release anyway.<br>
<br>
Four months is a compromise between avoiding bugfix releases and getting new<br>
features released.<br>
<br>
<br>
Jürgen<br>
<br>
--<br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br>
Software Engineer D-26506 Norden <a href="http://www.norbit.de" target="_blank">http://www.norbit.de</a><br>
QGIS PSC member (RM) Germany IRC: jef on FreeNode<br>
<br>
--<br>
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH<br>
Rheinstrasse 13, 26506 Norden<br>
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502<br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>
</div>