<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:CADRrdKtvZU5jh-8USgAR_ZJdD2yQUVrCOKROByuwh4gx--soKw@mail.gmail.com">
<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 class="moz-txt-link-freetext" href="https://github.com/OSGeo/PROJ/pull/4323">https://github.com/OSGeo/PROJ/pull/4323</a> and
<a class="moz-txt-link-freetext" href="https://github.com/OSGeo/PROJ/pull/4324">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 class="moz-signature" cols="72"><a class="moz-txt-link-freetext" href="http://www.spatialys.com">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>
</body>
</html>