<div dir="ltr"><div>Sounds good.</div><div><span class="gmail-pl-token"><br></span></div><div><span class="gmail-pl-token">Do we still need this line?<br></span></div><div><span class="gmail-pl-token">"Also</span> <span class="gmail-pl-token">update</span> <span class="gmail-pl-token">the</span> <span class="gmail-pl-token">redirect</span> <span class="gmail-pl-token">for</span> <span class="gmail-pl-s">`</span><span class="gmail-pl-c1">/* -> /<span class="gmail-pl-token">en</span>/<span class="gmail-pl-token">X</span>.<span class="gmail-pl-token">Y</span>/:<span class="gmail-pl-token">splat</span></span><span class="gmail-pl-s">`</span> <span class="gmail-pl-token">at ..."</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 16 Nov 2024 at 14:35, 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"><u></u>

  
    
  
  <div>
    <br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div>Wouldn't it be easier with a "tag" ? Just set (or re-set
            with -f) the tag "stable" to the needed commit (that can be
            another tag, like "9.5.1")<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>Yes tagging the new commit in 9.5 as "stable" would be slightly
      quicker. But that *can't* be labelled as 9.5.1, because we issue
      such SemVer tags to match official releases (with a tarball etc).</p>
    <p>I've finally successfully experimented some automation with a
      workflow that automatically refreshes the tag when a push is done
      in the 9.5 branch. See <a href="https://github.com/OSGeo/PROJ/pull/4323" target="_blank">https://github.com/OSGeo/PROJ/pull/4323</a> and
      <a href="https://github.com/OSGeo/PROJ/pull/4324" target="_blank">https://github.com/OSGeo/PROJ/pull/4324</a>. This adds 2 extra steps
      when creating a new maintenance branch, but apart from that, that
      should be transparent afterwards.</p>
    --
    <pre cols="72"><a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.</pre>
  </div>

</blockquote></div>