<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Jun 2020, at 07:38, Alessandro Pasotti <<a href="mailto:apasotti@gmail.com" class="">apasotti@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Nyall,<br class=""><br class="">Thank you for raising the issue, I agree that we need to make the<br class="">policy explicit (and discuss it if there is no consensus).<br class=""><br class="">I also agree that we need someone that makes the decisions in case<br class="">it's not clear or there is no agreement on if a commit can be<br class="">dangerous to backport.<br class=""><br class="">The most important thing is that we write this policy down somewhere<br class="">(the developers documentation?), it's just frustrating that one needs<br class="">to respect a list of unwritten rules that haven't been discussed or<br class="">approved by the community.<br class=""></div></div></blockquote><div><br class=""></div><div>Yes you are right. Maybe the process should be to first vote on it in PSC if needed and note it in </div><div><br class=""></div><div><a href="https://qgis.org/en/site/getinvolved/governance/resolutions/2020_resolutions.html?highlight=resolutions" class="">https://qgis.org/en/site/getinvolved/governance/resolutions/2020_resolutions.html?highlight=resolutions</a></div><div><br class=""></div><div>And then secondly start a ‘Community Rules and Standards’ page or similar where we lay out all these things in one place. Another candidate for recording this could be:</div><div><br class=""></div><div><a href="https://qgis.org/en/site/getinvolved/governance/governance.html?highlight=roles" class="">https://qgis.org/en/site/getinvolved/governance/governance.html?highlight=roles</a></div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Cheers<br class=""><br class="">On Fri, Jun 5, 2020 at 11:43 PM Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" class="">nyall.dawson@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">Hi PSC,<br class=""><br class="">I'd like to raise the notion that <a href="http://qgis.org" class="">qgis.org</a> appoint a formal position<br class="">for a release "traffic controller". This role would be responsible<br class="">for:<br class=""><br class="">1. Making the final call on what is suitable for backporting to stable releases<br class="">2. Guide formal policy regarding the different stages in the lifetime<br class="">of an LTR release, and develop written guidelines on what is<br class="">acceptable to backport at different patch releases for an LTR<br class="">3. Make the final call on feature freeze exemptions during a<br class="">pre-release freeze period.<br class=""><br class="">Some clarifications:<br class="">- This role would be distinct from the release manager position, which<br class="">is currently responsible for making QGIS releases, release packaging<br class="">and release cycles. This would be a time-intensive role, and I don't<br class="">think it should be added to the already (time-intensive) duties of the<br class="">release manager position.<br class="">- It would be a highly technical, very hands-on role, requiring<br class="">**daily/bi-daily** monitoring of the pull request queue and issue<br class="">tracker and full knowledge across all different parts of the QGIS<br class="">codebase and the interplay between them (and the risks associated with<br class="">changes). It is NOT a "project manager for QGIS" type role!<br class="">- It would be a formal community role appointed by PSC, not a position<br class="">on the PSC/board itself<br class=""><br class="">I'm raising this now after reflecting on the recent informal practice<br class="">that Matthias Kuhn and I have been trialling where non-crash,<br class="">non-data-corruption, non-trivial fixes get put into a "time delay"<br class="">before being allowed to included in an LTR patch release. (see<br class=""><a href="https://github.com/qgis/QGIS/pull/36718" class="">https://github.com/qgis/QGIS/pull/36718</a>,<br class=""><a href="https://github.com/qgis/QGIS/pull/36812" class="">https://github.com/qgis/QGIS/pull/36812</a>). By doing this, we ensure<br class="">that these fixes have exposure in a standard (non LTR) release for at<br class="">least one month before they get included in the LTR release. The<br class="">intention is to dramatically reduce the risk of regressions being<br class="">introduced in the middle of an LTR release. (When this happens, it<br class="">undermines user/enterprise confidence in the LTR process and reflects<br class="">poorly on QGIS). This is a completely informal policy we developed and<br class="">wanted to trial, and while I totally stand behind it and think it's a<br class="">great way approach it makes me nervous that Matthias and I have<br class="">basically just forced this policy ourselves. See<br class=""><a href="https://github.com/qgis/QGIS/pull/36718#issuecomment-639428003" class="">https://github.com/qgis/QGIS/pull/36718#issuecomment-639428003</a> for<br class="">discussion on this whether this policy is acceptable or not.<br class=""><br class="">IMO, suitable candidates would be developers with extensive experience<br class="">across a whole range of areas of the QGIS code, and demonstrated<br class="">history of timely reviews and responses to comments on github. I would<br class="">suggest that suitable candidates, (based on activity on github over<br class="">the past 12+ months and commits ranging across all areas of QGIS) are:<br class="">- Matthias<br class="">- Alessandro<br class="">- Denis<br class="">- (myself)<br class=""><br class="">Thanks for your consideration!<br class="">Nyall<br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Alessandro Pasotti<br class="">QCooperative: <a href="http://www.qcooperative.net" class="">www.qcooperative.net</a><br class="">ItOpen: <a href="http://www.itopen.it" class="">www.itopen.it</a><br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-psc</div></div></blockquote></div><br class=""><div class="">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 18px;"> </span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><span><img apple-inline="yes" id="CD38CEE2-1E6F-4444-B7B7-EDBB1FAACA11" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;">
</span></div>
<br class=""></body></html>