You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@datasketches.apache.org by tison <wa...@gmail.com> on 2026/01/09 10:47:38 UTC

Cleanup svn dev dir after release candidates confirmed or cancelled

Hi,

I noticed that we have many legacy release candidates on
https://dist.apache.org/repos/dist/dev/datasketches/.

Generally, we care about the final approved version, which goes to
https://dist.apache.org/repos/dist/release/datasketches/ (and later
https://archive.apache.org/dist/datasketches/).

I encountered a less-than-awesome experience today to set up the
release environment, where

    svn co https://dist.apache.org/repos/dist/dev/datasketches/ datasketches-dev

... takes a long time to download those unrelated files.

Surely I can check only the relevant files, but perhaps we should
clean up those legacy stashed RCs.

What do you think?

PS. In OpenDAL, we use svn mv [1] so that it's done when finalizing the release.

[2] https://opendal.apache.org/community/release/#publish-artifacts-to-svn-release-branch

Best,
tison.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
For additional commands, e-mail: dev-help@datasketches.apache.org


Re: Cleanup svn dev dir after release candidates confirmed or cancelled

Posted by Lee Rhodes <le...@gmail.com>.
Let me discuss with Alex and Jon, but I think we can clean this up.

On Fri, Jan 9, 2026 at 2:59 AM tison <wa...@gmail.com> wrote:

> As a workaround, I run:
>
>   svn co https://dist.apache.org/repos/dist/dev/datasketches/
> datasketches-dev --depth=empty
>   svn update KEYS
>   svn update scripts
>   svn update rust
>
> Just in case you're interested in checking out partially.
>
> Best,
> tison.
>
> tison <wa...@gmail.com> 于2026年1月9日周五 18:47写道:
> >
> > Hi,
> >
> > I noticed that we have many legacy release candidates on
> > https://dist.apache.org/repos/dist/dev/datasketches/.
> >
> > Generally, we care about the final approved version, which goes to
> > https://dist.apache.org/repos/dist/release/datasketches/ (and later
> > https://archive.apache.org/dist/datasketches/).
> >
> > I encountered a less-than-awesome experience today to set up the
> > release environment, where
> >
> >     svn co https://dist.apache.org/repos/dist/dev/datasketches/
> datasketches-dev
> >
> > ... takes a long time to download those unrelated files.
> >
> > Surely I can check only the relevant files, but perhaps we should
> > clean up those legacy stashed RCs.
> >
> > What do you think?
> >
> > PS. In OpenDAL, we use svn mv [1] so that it's done when finalizing the
> release.
> >
> > [2]
> https://opendal.apache.org/community/release/#publish-artifacts-to-svn-release-branch
> >
> > Best,
> > tison.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
> For additional commands, e-mail: dev-help@datasketches.apache.org
>
>

Re: Cleanup svn dev dir after release candidates confirmed or cancelled

Posted by tison <wa...@gmail.com>.
As a workaround, I run:

  svn co https://dist.apache.org/repos/dist/dev/datasketches/
datasketches-dev --depth=empty
  svn update KEYS
  svn update scripts
  svn update rust

Just in case you're interested in checking out partially.

Best,
tison.

tison <wa...@gmail.com> 于2026年1月9日周五 18:47写道:
>
> Hi,
>
> I noticed that we have many legacy release candidates on
> https://dist.apache.org/repos/dist/dev/datasketches/.
>
> Generally, we care about the final approved version, which goes to
> https://dist.apache.org/repos/dist/release/datasketches/ (and later
> https://archive.apache.org/dist/datasketches/).
>
> I encountered a less-than-awesome experience today to set up the
> release environment, where
>
>     svn co https://dist.apache.org/repos/dist/dev/datasketches/ datasketches-dev
>
> ... takes a long time to download those unrelated files.
>
> Surely I can check only the relevant files, but perhaps we should
> clean up those legacy stashed RCs.
>
> What do you think?
>
> PS. In OpenDAL, we use svn mv [1] so that it's done when finalizing the release.
>
> [2] https://opendal.apache.org/community/release/#publish-artifacts-to-svn-release-branch
>
> Best,
> tison.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
For additional commands, e-mail: dev-help@datasketches.apache.org