Cleaning up EOL releases

[Baptiste Jonglez]

On 31-01-26, Paul Spooren wrote:
> Hi,
> 
> > On 30. Jan 2026, at 19:47, Baptiste Jonglez <baptiste at bitsofnetworks.org> wrote:
> > 
> > Hi,
> > 
> > I would like to clean up the following snapshot releases on the download
> > server since they are end-of-life (see [1]):
> > 
> > 21.02-SNAPSHOT
> > 22.03-SNAPSHOT
> > 23.05-SNAPSHOT
> > 
> > Unless there are objections, I will go ahead in one week.
> 
> Sounds good, thanks! Just wondering, are there any commits after the latest point release? 

Yes.  If you mean that 23.05-SNAPSHOT is more recent than the last
release, indeed:

- 16 August 2025 for 23.05.6
- 9 December 2025 for the last build of 23.05-SNAPSHOT (before it got removed from buildbot)

However it's untested/unsupported.

> > Also, as a longer-term goal, we need to think about removing old releases
> > from the main download server (we currently have everything since 17.01,
> > and it's taking a lot of disk space as well as slowing down rsync).  Since
> > early January, we already redirect CDN downloads to the archive server for
> > old releases.  But I would also like to serve these old releases through
> > rsync, in case somebody is interested in historical analysis.
> 
> This sounds like a niche use case where a recursive wget would also do the trick?

As long as there is some reasonably efficient way to get them (and
preferably several ways for redundancy), sure.  Could be a combination of
archive.openwrt.org, archive.org, and object storage paid by the project.

> > As a first step, we could start removing -rc releases, since they already
> > take significant space, and nobody is supposed to stay on -rc releases
> > once a stable major release is out.  With the new mirror setup [2], we
> > already exclude these old -rc releases from the "default mirror set".
> 
> While doing these clean ups, should we also upload things to archive.org?
> 
> Paul
>