<div dir="ltr">Hey Jurgen,<br><br>That sounds really good to me. The auto release based on silence in the branch sounds like a good idea. Given that this is the first time we have done this I think we will just need to iron out any issues as we find them, hard to get things right on the first run.<div><br></div><div>- Nathan</div></div><br><div class="gmail_quote">On Mon, 2 Mar 2015 at 23:00 Jürgen E. <<a href="mailto:jef@norbit.de">jef@norbit.de</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I started to including the LTR release in the packaging/nightly builds. I'm<br>
going to change the plan/procedure a bit. Both regular release and ltr will<br>
be branched of master and continue to be called release-$major_$minor. The LTR<br>
additionally gets a ltr-$major_$minor tag. <a href="http://release.pl" target="_blank">release.pl</a> is already changed that<br>
way any release-2_8 has such a tag.<br>
<br>
A cronjob will monitor release branches for changes and intiate a new point<br>
release whenever there are two week silence after a new commit (or manually<br>
when there was a very important fix).<br>
<br>
The nightly builds will monitor master, latest release and ltr branch and<br>
create nightly packages if there are changes (1+2+4), unless there was a<br>
version change (ie. a point release) in which case regular packages will be<br>
made (3+5).<br>
<br>
For Windows there will be five different packages (1-5: qgis-dev, qgis-rel-dev,<br>
qgis, qgis-ltr-dev, qgis-ltr) in OSGeo4W, for debian/ubuntu there will be five<br>
different repositories (1-5: debian-nightly, debian-nightly-release, debian,<br>
debian-lts-nightly, debian-lts).<br>
<br>
4+5 are only made if the latest release and ltr branch are different. Until<br>
then latest release and ltr are identical anyway. That also means ltr packages<br>
only start four months after a ltr release happened and we maintain the ltr<br>
branch four months as our regular and nine specifically as separate ltr<br>
release. That also implies that installing ltr packages means that you install<br>
something that already has seen four months of maintainance.<br>
<br>
An open question is what to do in the four month a new ltr is out. While there<br>
is no new regular release only regular packages are created and there are no<br>
new ltr packages. This might be negligible as the ltr branch will have been<br>
maintained for a year as promised, but if you only install ltr packages there<br>
will be a gap of four months without updates. But I guess that can be left<br>
open until we get there.<br>
<br>
Thoughts?<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 release manager (PSC) Germany IRC: jef on FreeNode<br>
______________________________<u></u>_________________<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/<u></u>mailman/listinfo/qgis-<u></u>developer</a></blockquote></div>