You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by Karol Brejna <ka...@apache.org> on 2017/06/23 16:59:54 UTC
svn dev repo cleanups
I am preparing artifacts for 0.8.4 release.
On of the steps is to publish them to svn.
In order to publish, you need to check out svn repo (which in turn
pull all files stored there).
The files got quite sizeble:
575180 gearpump/.svn
185280 gearpump/0.8.2-incubating
245708 gearpump/0.8.3-incubating
So it's about 1GB worth of files which transfer takes quite a long time.
I am proposing enriching our release procedure with a step of cleaning
release artifacts after the release.
After release we move
Re: svn dev repo cleanups
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi guys,
dist.apache.org should contain only the latest release.
It's automatically backup on archive.apache.org, it's where you can find
previous releases.
For instance:
https://dist.apache.org/repos/dist/release/karaf/4.1.1/
is the latest Karaf release and:
http://archive.apache.org/dist/karaf/
contains previous releases that happened on dist.apache.org.
Regards
JB
On 06/24/2017 04:33 AM, Manu Zhang wrote:
> That's good idea. I've checked other project and it seems they don't keep
> release candidates.
>
> @JB(+jb@nanthrax.net <ma...@nanthrax.net>), any guideline or convention for
> this ?
>
> On Sat, Jun 24, 2017 at 1:05 AM Karol Brejna <karolbrejna@apache.org
> <ma...@apache.org>> wrote:
>
> (continued)
>
> ... the artifacts from
> https://dist.apache.org/repos/dist/dev/incubator/gearpump' to
> https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
> so we don't loose any historical data.
>
> The situation is worse when we have multiple release
> candidates.Erasing the old artifacts would quicken the release
> procedure.
>
> Please, tell me what you think.
>
> Karol
>
> On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna <karolbrejna@apache.org
> <ma...@apache.org>> wrote:
> > I am preparing artifacts for 0.8.4 release.
> >
> > On of the steps is to publish them to svn.
> > In order to publish, you need to check out svn repo (which in turn
> > pull all files stored there).
> >
> > The files got quite sizeble:
> >
> > 575180 gearpump/.svn
> > 185280 gearpump/0.8.2-incubating
> > 245708 gearpump/0.8.3-incubating
> >
> >
> > So it's about 1GB worth of files which transfer takes quite a long time.
> >
> > I am proposing enriching our release procedure with a step of cleaning
> > release artifacts after the release.
> >
> > After release we move
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: svn dev repo cleanups
Posted by Manu Zhang <ow...@gmail.com>.
That's good idea. I've checked other project and it seems they don't keep
release candidates.
@JB(+jb@nanthrax.net <jb...@nanthrax.net>), any guideline or convention for
this ?
On Sat, Jun 24, 2017 at 1:05 AM Karol Brejna <ka...@apache.org> wrote:
> (continued)
>
> ... the artifacts from
> https://dist.apache.org/repos/dist/dev/incubator/gearpump' to
> https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
> so we don't loose any historical data.
>
> The situation is worse when we have multiple release
> candidates.Erasing the old artifacts would quicken the release
> procedure.
>
> Please, tell me what you think.
>
> Karol
>
> On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna <ka...@apache.org>
> wrote:
> > I am preparing artifacts for 0.8.4 release.
> >
> > On of the steps is to publish them to svn.
> > In order to publish, you need to check out svn repo (which in turn
> > pull all files stored there).
> >
> > The files got quite sizeble:
> >
> > 575180 gearpump/.svn
> > 185280 gearpump/0.8.2-incubating
> > 245708 gearpump/0.8.3-incubating
> >
> >
> > So it's about 1GB worth of files which transfer takes quite a long time.
> >
> > I am proposing enriching our release procedure with a step of cleaning
> > release artifacts after the release.
> >
> > After release we move
>
Re: svn dev repo cleanups
Posted by Karol Brejna <ka...@apache.org>.
(continued)
... the artifacts from
https://dist.apache.org/repos/dist/dev/incubator/gearpump' to
https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
so we don't loose any historical data.
The situation is worse when we have multiple release
candidates.Erasing the old artifacts would quicken the release
procedure.
Please, tell me what you think.
Karol
On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna <ka...@apache.org> wrote:
> I am preparing artifacts for 0.8.4 release.
>
> On of the steps is to publish them to svn.
> In order to publish, you need to check out svn repo (which in turn
> pull all files stored there).
>
> The files got quite sizeble:
>
> 575180 gearpump/.svn
> 185280 gearpump/0.8.2-incubating
> 245708 gearpump/0.8.3-incubating
>
>
> So it's about 1GB worth of files which transfer takes quite a long time.
>
> I am proposing enriching our release procedure with a step of cleaning
> release artifacts after the release.
>
> After release we move