<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I think we can do a little bit of fine-tuning. I’ve added an extra commit to the branch with my additions:<div><br></div><div style="display: block;"><a href="https://github.com/OSGeo/PROJ/pull/4369/commits/8f045bac73d2823d1d3ee17b3537b5d58d902995">https://github.com/OSGeo/PROJ/pull/4369/commits/8f045bac73d2823d1d3ee17b3537b5d58d902995</a></div><div style="display: block;"><br></div><div style="display: block;">I’ve clarified that a change in version requirements needs to be communicated clearly and removed a line</div><div style="display: block;">about changing versions of programming languages that contradicts the reason why we are updating this RFC</div><div style="display: block;">In the first place.</div><div style="display: block;"><br></div><div style="display: block;">With those details added I am +1 as well.</div><div style="display: block;"><br></div><div style="display: block;">/Kristian</div><div><div><br><blockquote type="cite"><div>On 7 Jan 2025, at 04.48, Even Rouault via PROJ <proj@lists.osgeo.org> wrote:</div><br class="Apple-interchange-newline"><div><div><br>Le 07/01/2025 à 04:37, Alan Snow a écrit :<br><blockquote type="cite">At first glance, it seems reasonable. Though I have a couple of questions for clarification.<br><br>Would it make sense to word the RFC so we prefer making dependency changes on major releases, but exceptions can be made? For example, if the dependency charge can be classified as a minor change and will cause minimal disruptions, then an exception can be made.<br><br>What were the reasons for originally wanting to only apply dependency updates for major releases? How do we plan to ensure the original reasons are not overlooked for minor releases?<br></blockquote><br>IMHO spending more time fine-tuning RFC-3 is not worth it. Our usual communication mechanisms, pull requests or messages on this list, and seeking for enough consensus, and making a motion if needed, are enough to handle those situations.<br><br>-- <br>http://www.spatialys.com<br>My software is free, but my time generally not.<br>Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.<br><br>_______________________________________________<br>PROJ mailing list<br>PROJ@lists.osgeo.org<br>https://lists.osgeo.org/mailman/listinfo/proj<br></div></div></blockquote></div><br></div></body></html>