Have new release published in /source/old directory too?

[Yann Ylavic]

On Thu, Apr 23, 2020 at 5:12 PM Dr. Matthias St. Pierre
<Matthias.St.Pierre at ncp-e.com> wrote:
>
> > For each new release, it seems that the tarball is published in the
> > "/source" directory (website) while the previous one is moved to
> > "/source/old/<series>".
> >
> > Would it be possible that all releases land in "/source/old",
> > including the new one when published? After all anything is more or
> > less old, as soon as it's born ;)
>
>
> Normally, you should be able to access older releases without changing the URL,
> (even after they were moved) because there is an URL rewrite rule which handles this.
>
> For an example, 1.1.1a is available at the same location as 1.1.1g:
>
> ~/tmp$ curl -JOL https://www.openssl.org/source/openssl-1.1.1g.tar.gz
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>  Dload  Upload   Total   Spent    Left  Speed
> 100 9571k  100 9571k    0     0  1992k      0  0:00:04  0:00:04 --:--:-- 1992k
>
> ~/tmp$ curl -JOL https://www.openssl.org/source/openssl-1.1.1a.tar.gz
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>  Dload  Upload   Total   Spent    Left  Speed
> 100 8154k  100 8154k    0     0  4962k      0  0:00:01  0:00:01 --:--:-- 4960k
>
> Concidentally, a few days ago the rewrite rule was broken, but that has been fixed.
> (see https://github.com/openssl/openssl/issues/11521#issuecomment-612483438 and ff.)

OK, that explains. Actually I had the issue from 1.1.1e to 1.1.1f and
changed the script.
Looking again at the changes now they look.. ugly, so I thought I'd ask.

All I need is a persistent URL base, so thanks!

Regards,
Yann.