<div dir="ltr"><div class="gmail_extra"><div>Hi Jürgen,</div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Fixes and features are released every four months - including a four weeks window for testing and fixing. Which is of course not as good as LTS, but it's apparently feasible and working.</blockquote></div><div><br></div>
<div>But is it working? I believe the point of an LTS is that each version is more stable than the last and that there are no new features which in turn means no new bugs should be introduced. Everyone wants QGIS to be stable of course, but adding new features by definition isn't going to be compatible with that - New features introduce new bugs irrespective of the amount of testing there is. It's far less common (but by no means unknown) for a bugfix to introduce a new bug.<br>
</div><div><br></div><div>I don't know the story of why having two branches failed in the past, but the fact that this topic is raised every couple of months by new people should indicate that there's a strong desire for it within the community, so maybe it's worth investigating again.</div>
<div>What caused it to fail last time? Is there anything the community can learn from that? Can QGIS learn from any of the other Open Source communities that successfully maintain multiple branches? What resources are needed to make it happen?</div>
<div><br></div><div>Cheers,</div><div>Jonathan</div>
<br><br><div class="gmail_quote">On 22 July 2014 11:16, Jürgen E. <span dir="ltr"><<a href="mailto:jef@norbit.de" target="_blank">jef@norbit.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Lene,<br>
<div class=""><br>
On Mon, 21. Jul 2014 at 15:35:55 +0000, Lene Fischer wrote:<br>
> What if we had :<br>
> · A long term stable version for ex. 12 months with bugfix only<br>
> · A developer version for 4 months with new features and bugfixes => Stable<br>
</div>> version with short bugfix-period => New developer??????..<br>
<br>
Not much news there. This comes up again and again.<br>
<br>
We already tried to maintain two branches in the past and failed. I'm not sure<br>
if we still would, but I don't see any big changes that makes it less likely<br>
either.<br>
<br>
And that's why we have the tight release schedule now - it's there to both get<br>
bugfixes out and new features in in a reasonable time frame and with minimum<br>
extra or duplicate effort (which backports and packing are - not a awful lot,<br>
but some).<br>
<br>
Fixes and features are released every four months - including a four weeks<br>
window for testing and fixing. Which is of course not as good as LTS, but it's<br>
apparently feasible and working.<br>
<br>
<br>
Jürgen<br>
<span class=""><font color="#888888"><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 release manager (PSC) 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>
</font></span><div class=""><div class="h5"><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">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>
</div></div></blockquote></div><br></div></div>
<br>
<span style="color:rgb(34,34,34);font-family:Arial;background-color:rgb(255,255,255)">This transmission is intended for the named addressee(s) only and may contain confidential, sensitive or personal information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.</span>