Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: Stefan Bodewig <bodewig@apache.org>
To: dev@ant.apache.org
Subject: Re: Mandatory svnpubsub migration by Jan 2013
References: <1328704008.78327.YahooMailNeo@web160901.mail.bf1.yahoo.com>
	<0706FA04-3AAC-4CB4-885D-6E972F0C8751@hibnet.org>
Date: Tue, 21 Feb 2012 16:52:16 +0100
In-Reply-To: <0706FA04-3AAC-4CB4-885D-6E972F0C8751@hibnet.org> ("Nicolas
	=?utf-8?Q?Lalev=C3=A9e=22's?= message of "Mon, 20 Feb 2012 13:35:25 +0100")
Message-ID: <871upofakv.fsf@v35516.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2012-02-20, Nicolas Lalev=C3=A9e wrote:

> We already did the migration of our sites to svnpubsub. We still need
> to migrate our dist folder.

> AFAIU it is quite trivial. Instead of putting files manually into
> people.a.o:/www/www.apache.org/dist/ant/ we would have to commit them
> into a svn [1]. Deleting files from our main dist is just about doing
> some svn rm. And the ASF archive doesn't apply the svn rm so
> everything committed once gets into the archive.

That's my understanding as well.

> And if we are willing to, we have at our disposal de "dev" space where
> release to be voted upon can be "staged" [2]. And once the vote pass,
> just a "svn cp dev/xxx release/xxx && svn rm dev/xxx" does the
> actually publishing (it seems there are restrictions on svn mv).

I know I'd be using that rather than my user space on people.ao

> A thing to note though: I guess that with svnpubsub, we cannot have
> symlinks

The "-current" symlinks are frownded upon by now anyway.  They seem to
mess up mirrors.  We could easily live without them IMHO.

> We then just need to create an INFRA ticket asking for the
> transition. I guess we want the svn notifications sent to
> notifications@ant.apache.org. Once the infra has created our space, we
> would just need to check in the current content of our dist.

Currently KEYS is a (sym)link to a checked out copy from somewhere else.
Once we have svnpubsub in place I'd suggest we make the dist repository
the canonical place for storing PGP keys.

> A side effect will probably that ivy/updatesite/trunk/dist will
> disappeared from our svn. Maybe it would help in the management of the
> new Eclipse update site [3] [4].

Is this something that has to be resolved before the transition?  If so,
don't rush it - we still have a few months until the migration must be
complete.

> I willing to ask for the migration this week unless there's some
> concern.

No concerns except for the Eclipse update site that I don't understand
anyway ;-)

Stefan

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