<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 15 Nov 2024 at 13:30, 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>
Javier,
<blockquote type="cite">
<div dir="ltr">
<div>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;white-space:pre-wrap"><span style="font-family:arial,sans-serif">I have the impression (maybe I misunderstood) that both the automatic redirection and the robots should be pointing to "stable". (GDAL didn't have "stable" url at the beginning, I know)
</span></pre>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;white-space:pre-wrap"><span style="font-family:arial,sans-serif">That will make search engine indexers don't have to remake the index, with the consequent degradation in the position. Also will not point somebody to an old version of the software. It is good that the old versions are there in case you need it, but search engines should point to "stable" (and IMHO not to latest, with functionalities that are may not be released yet).
</span></pre>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;white-space:pre-wrap"><span style="font-family:arial,sans-serif">What do you think?
</span></pre>
</div>
</div>
</blockquote>
The annoying thing with "stable" is that it points to the latest
released *tag*, not the head of the release branch, so bugfixes in
the doc after the release don't appear until the next one.<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;white-space:pre-wrap"><span style="font-family:arial,sans-serif">
</span></pre>
<pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;white-space:pre-wrap"><span style="font-family:arial,sans-serif">There was a problem in PROJ after the last release. Maybe we can fix it to be ready for the next release in a couple of weeks.
</span></pre>
</div>
</div>
</blockquote>
<p>Refresh our minds about which problem you're thinking too (don't
we spend our time solving problems) :-) ?</p>
<p>One problem I've in mind with the "stable" RTD tag is that when
you prepare the release, you need in advance to update the doc to
advertize the release *before* creating the tag. For example
<a href="https://proj.org/en/stable/download.html" target="_blank">https://proj.org/en/stable/download.html</a> doesn't point to the
9.5.0 release, because the commit that advertizes it was done just
after. For GDAL, I've adjusted the release procedure so that step
is done in advance.</p>
<p>Bottom line: I would be in favor of pointing to "stable" if we
could tweak the RTD configuration to point to a branch of our
choice, but I don't think that's currently possible.</p>
<p>Another thought: the GDAL user survey currently advertized on
<a href="http://gdal.org" target="_blank">gdal.org</a> couldn't be advertized if the default was the stable RTD
tag</p>
<p>EDIT: actually looking at
<a href="https://docs.readthedocs.io/en/stable/versions.html" target="_blank">https://docs.readthedocs.io/en/stable/versions.html</a>, I do read "If
you want a custom <code class="gmail-notranslate"><span>stable</span></code> version,
create either a tag or branch in your project with that name.". So
maybe we should just create a git "stable" branch, but that means
we need to regularly resync it to the actual HEAD of the active
9.x git branch<br></p></div></blockquote><div>Looks like you found the proper and nice way to do it, right? Using a tag (or branch) called "stable". I think that the overhead of the release process is minimal. In PROJ it would replace the penultimate line from <a href="https://github.com/OSGeo/PROJ/blob/master/HOWTO-RELEASE.md">https://github.com/OSGeo/PROJ/blob/master/HOWTO-RELEASE.md</a> if I understood correctly.<br></div><div><br></div><div>Do not forget about robots.txt allowing only stable. I think it would make the indexing more stable (no pun intended initially. Now yes ;), and the user experience better (finding always "stable", and not an old branch)<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
</p>
<span style="white-space:pre-wrap">
</span>
<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></div>