The older releases are still easily gotten from archive.apache.org. Let's just keep the current release from the branch on the mirrors.
On Tue, Mar 3, 2020 at 10:31 AM Andrew Purtell <[email protected]> wrote: > > Greetings, > > Now that branch-1 releases, typically, will be renumbered at each release > point with a new minor version, e.g. 1.5.0, 1.6.0, 1.7.0..., what do you > think is appropriate as a retention policy for older release artifacts > under dist/. > > Previously we retained the latest patch version for each active code line, > and so retained one version for every minor version. For example, if 1.2, > 1.3, and 1.4 were active we would have one 1.2.x, one 1.3.x, and one 1.4.x. > For each minor release we used to make a releasing branch for it, and we > would retain one version for each branch. > > I propose an analogous policy considering branch-1 is now the releasing > branch. As before, there would be only one version retained in dist/ for > the releasing branch, the latest. Accordingly with the release of 1.6.0 we > should delete the 1.5.0 artifacts under dist/. > > Or would you prefer we keep an additional version? For example, with the > release of 1.6.0, we could keep 1.5.0 and 1.6.0, but upon the release of > 1.7.0, we would remove 1.5.0. > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk
