Hi PJ,

I have cleaned up both [dev] and [release]. Repository [dev] has been
emptied,
while repository [release] retains the latest released version (0.10.3).

Later, I will submit a PR to add this operation step (cleaning up old
releases) to the doc.

[dev] https://dist.apache.org/repos/dist/dev/incubator/fury/
[release] https://dist.apache.org/repos/dist/release/incubator/fury/

On Wed, May 28, 2025 at 8:30 PM PJ Fanning <[email protected]> wrote:

> Thanks Liangliang Sui. The release management doc is at:
> https://fury.apache.org/docs/community/how_to_release/
>
> This mentions where the svn repo is (dist.apache.org). You can use
> `svn rm` to remove old files but this needs an `svn commit` to commit
> the change to the repo.
> Ideally, the doc page should be updated to mention the removal of old
> releases.
>
> When I do releases, I typically leave the last release there until
> after the download page has been updated to point to the new release
> and then circle back to remove the old release.
>
> On Wed, 28 May 2025 at 13:11, Liangliang Sui <[email protected]>
> wrote:
> >
> > Hi PJ,
> >
> > Thanks for pointing this out.
> > I will take over this issue and learn how to clean up old releases.
> >
> > Best,
> > Liangliang Sui
> >
> > On Wed, May 28, 2025 at 6:26 PM PJ Fanning <[email protected]> wrote:
> >
> > > You'll see the issue highlighted in the Fury clutch report:
> > >
> > > https://incubator.apache.org/clutch/fury.html
> > >
> > > There is a requirement to clear out old releases and only keep the most
> > > recent one.
> > > The older releases are archived automatically and
> > > https://fury.apache.org/download/ already has a link to that.
> > >
> > > Would someone in the PPMC be able to take a look?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to