Mailing-List: contact dev-help@gearpump.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@gearpump.incubator.apache.org
MIME-Version: 1.0
References: <CAH3zwfJWZFaVmGCQ2H9KNyshfKtscw0-ZyOjermP7hZXudetVQ@mail.gmail.com>
 <CAH3zwfJc78j+N45b8j-d_4bcMvadpQpkLax96bO5=4+sUpn-wA@mail.gmail.com>
In-Reply-To: <CAH3zwfJc78j+N45b8j-d_4bcMvadpQpkLax96bO5=4+sUpn-wA@mail.gmail.com>
From: Manu Zhang <owenzhang1990@gmail.com>
Date: Sat, 24 Jun 2017 02:33:26 +0000
Message-ID: <CABT57mZpsEv+xYjE5m5mi5Vv0RoyQMVrx5ZvE_VDQcGYndS0MQ@mail.gmail.com>
Subject: Re: svn dev repo cleanups
To: dev@gearpump.incubator.apache.org, "jb@nanthrax.net" <jb@nanthrax.net>
Content-Type: multipart/alternative; boundary="94eb2c0740be86b0040552ab8b50"
archived-at: Sat, 24 Jun 2017 02:33:44 -0000

--94eb2c0740be86b0040552ab8b50
Content-Type: text/plain; charset="UTF-8"

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 <karolbrejna@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>
> 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
>

--94eb2c0740be86b0040552ab8b50--