<div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 2, 2019 at 12:22 PM Even Rouault <<a href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> And at this stage in the life of the LTR I just<br>
> don't see the risks of regressions outweighing anything but<br>
> crash/corruption fixes.<br>
<br>
"Stage" is the keyword here. Number of software vendors have generally several <br>
stages during the lifetime of the product they support, generally a first one <br>
which is the polishing of the release where they can even add new features, <br>
another one where they only backport (critical) bug fixes, and a final one <br>
where they only backport security related bug fixes.<br>
<br>
So, maybe we could have a 2 phase process:<br>
- First 6 months: backport of bug fixes with the same criteria as we do <br>
currently<br>
- Last 6 months: only critical bug fixes (crashes, data loss)<br>
<br>
(or 9 months / 3 months, whatever...)<br>
<br></blockquote><div><br></div><div>This looks a good approach to me.</div><div></div><div><div><br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
But if we're really in that mode, that should not only apply to QGIS but to <br>
its dependent libraries as well. Basically this would mean that for OSGeo4W, <br>
you should have 2 distinct sets for the dependencies: one frozen (or with very <br>
controlled changes) for the LTR, and a living one for the new versions.<br>
<br>
Even<br></blockquote><div><br></div><div>Yes, that makes sense too.</div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><div></div></div><div></div><div><br></div><div>-- <br><div dir="ltr" class="gmail_signature">Alessandro Pasotti<br>w3: <a href="http://www.itopen.it" target="_blank">www.itopen.it</a></div></div></div>