<div dir="auto">Re-adding the unintentionally removed conversation to the list.<div dir="auto">Thanks Andreas!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 24, 2023, 08:36 Andreas Neumann <<a href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p>Hi Matthias,</p>
<p>My responses are below.</p>
<p id="m_-2771934724355744839reply-intro">On 2023-03-23 23:42, Matthias Kuhn wrote:</p>
<blockquote type="cite" style="padding:0 0.4em;border-left:#1010ff 2px solid;margin:0">
<div id="m_-2771934724355744839replybody1">
<div>
<div dir="auto">Hi,
<div dir="auto"> </div>
<div dir="auto">I agree with you that a monthly release makes sense, especially in the beginning, but I wonder if it makes sense to change that towards the end or if we can just stick to the once patch release per month that we currently have. Even at this stage, I think this can help.</div>
<div dir="auto"> </div>
</div>
</div>
</div>
</blockquote>
<div id="m_-2771934724355744839replybody1">
<div>
<div dir="auto">
<div dir="auto"> </div>
<div dir="auto">That would be fine with me as well: keep the monthly releases until the end of the life time of an LT version. That would probably make things easier for Jürgen.</div>
<div dir="auto"> </div>
</div>
</div>
</div>
<blockquote type="cite" style="padding:0 0.4em;border-left:#1010ff 2px solid;margin:0">
<div id="m_-2771934724355744839replybody1">
<div>
<div dir="auto">
<div dir="auto"> </div>
<div dir="auto"> </div>
<div dir="auto">As for releasing earlier for testing, I like the idea a lot but would not limit it to specific people but spread it as much as possible, labeled as "release candidate", 2-4 weeks before the final release to leave room for reaction and possibly a second rc.</div>
<div dir="auto"> </div>
</div>
</div>
</div>
</blockquote>
<div id="m_-2771934724355744839replybody1">
<div>
<div dir="auto">
<div dir="auto"> </div>
<div dir="auto">Ok, yes. That is also ok for me. And I think we already do that. The first version 3.0 has the label "release candidate" written on the Splash screen. So that is already covered. We just have to check websites and other communication if we handle the "release candidate" wording consistently.</div>
<div dir="auto"> </div>
<div dir="auto">This would then also be the response to Alex/Giovanni: they are not the only testers. All of the adventurous people who use the 3.xx.0 release are testing along with them. That would be ok with me. One has to expect issues with a .0 release. And the more people test, the more likely, issues are discovered.</div>
<div dir="auto"> </div>
<div dir="auto">Thanks,</div>
<div dir="auto">Andreas</div>
<div dir="auto"> </div>
</div>
</div>
</div>
<blockquote type="cite" style="padding:0 0.4em;border-left:#1010ff 2px solid;margin:0">
<div id="m_-2771934724355744839replybody1">
<div>
<div dir="auto">
<div dir="auto"> </div>
<div dir="auto"> </div>
<div dir="auto">Bests</div>
<div dir="auto">Matthias</div>
<div dir="auto"> </div>
<div dir="auto"> </div>
<br><br>
<div dir="auto">
<div dir="ltr">On Thu, Mar 23, 2023, 19:10 Andreas Neumann via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">qgis-psc@lists.osgeo.org</a>> wrote:</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p>Hi PSC and devs,</p>
<p>It seems like there is consensus that LT can/should be released more often. At least the testers Giovanni and Alex have nothing against releasing LT more often - and Jürgen has it automated. Nyall and myself (and probably others) are both for releasing more often - esp. in the light of the combination with the quarantine rule and one month delay that comes with the quarantine rule.</p>
<p>So Jürgen: May I please kindly ask you to adjust the road map ( <a href="https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule" rel="noopener noreferrer noreferrer" target="_blank">https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule</a> ) again - sorry about the back on forth in this respect.</p>
<p>This would mean:</p>
<p>3.28.5: 2023-03-31<br>3.28.6: 2023-04-28<br>3.28.7: 2023-05-26<br>3.28.8: 2023-06-23 --> switch to 4 month cycle<br>3.28.9: 2023-10-27 (last 3.28.x release)<br><br></p>
<p>This basically means that only the last quarter of the life span of an LT release would be released in the "thinned out" mode and the releases before still in the monthly cycle. In the last quarter of the life span of an LT version there are typically fewer backports, because hopefully the more severe issues are fixed before and it also gets more and more difficult to backport for devs.</p>
<p>Enterprise and gov users typically install after a version becomes LT (4 months after the initial release) - then they test and report issues. This means that in the middle of the life span of an LT version there is still a lot of feedback and fixes coming in - hence we need the monthly releases in this time period.</p>
<p>Thank you for your consideration - Jürgen!</p>
<p>Andreas</p>
</div>
_______________________________________________<br>QGIS-PSC mailing list<br><a href="mailto:QGIS-PSC@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">QGIS-PSC@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noopener noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></blockquote>
</div>
</div>
<br>
<div style="text-align:left"><span style="font-family:Arial"><a href="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/" rel="noopener noreferrer noreferrer" target="_blank"><img src="cid:1679643385641d52f95c38b075916605@carto.net" alt="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/"></a><br></span></div>
<div style="text-align:left"><span style="font-family:Arial">Best of Swiss Enterprise App-<a href="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/" rel="noopener noreferrer noreferrer" target="_blank">Award for QField</a>- Hold the power of QGIS in your hand</span><span style="font-family:Arial"> - <a href="https://qfield.org/get" rel="noopener noreferrer noreferrer" target="_blank">get it now</a><br></span></div>
</div>
</div>
</blockquote>
<p><br></p>
</div>
</blockquote></div>
<br>
<div style="text-align:left"><span style="font-family:Arial"><a href="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/" target="_blank"><img src="https://www.opengis.ch/wp-content/uploads/2022/11/Mail-Footer_OpenGIS_393x120_AppAward.png" alt="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/"></a><br></span></div><div style="text-align:left"><span style="font-family:Arial">Best of Swiss Enterprise App-<a href="https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/" target="_blank">Award for QField</a><span style="font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif"><font size="3"> </font></span>- Hold the power of QGIS in your hand</span><span style="font-family:Arial"> - <a href="https://qfield.org/get" target="_blank">get it now</a><br></span></div>