ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <>
Subject Re: Mandatory svnpubsub migration by Jan 2013
Date Mon, 20 Feb 2012 12:35:25 GMT
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/
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.

As it would be managed by svnpubsub, changes will be reflected quite immediately to,
as it does for our website. It won't change the mirroring delay though.

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).

A thing to note though: I guess that with svnpubsub, we cannot have symlinks (I have not ask
the infra, not find any mention of them in the sparse doc). We have some in people.a.o:/www/
On the other hand they doesn't appear on the site I guess
it's OK.

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

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].

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



Le 8 févr. 2012 à 13:26, Joe Schaefer a écrit :

> FYI: infrastructure policy regarding website hosting has
> changed as of November 2011: we are requiring all websites
> and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012.
> If your PMC has already met this requirement congratulations,
> you can ignore the remainder of this post.
> As stated on
> we are migrating our webserver infrastructure to 100% svnpubsub
> over the course of 2012.  If your site does not currently make
> use of this technology, it is time to consider a migration effort,
> as rsync-based sites will be PERMANENTLY FROZEN in Jan 2013 due 
> to infra disabling the hourly rsync jobs.  While we recommend
> migrating to the ASF CMS [0] for Anakia based or Confluence based
> sites, and have provided tooling [1] to help facilitate this,
> we are only mandating svnpubsub (which the CMS uses itself).
> svnpubsub is a client-server system whereby a client watches an
> svn working copy for relevant commit notifications from the svn
> server.  It subsequently runs svn up on the working copy, bringing
> in the relevant changes.  sites that use static build technologies
> that commit the build results to svn are naturally compatible with
> svnpubsub; simply file a JIRA ticket with INFRA to request a
> migration: any commits to the resulting build tree will be 
> instantly picked up on the live site.
> The CMS is a more elaborate system based on svnpubsub which
> provides a webgui for convenient online editing.  Dozens of
> sites have already successfully deployed using the CMS and
> are quite happy with the results.  The system is sufficiently
> flexible to accommodate a wide variety of choices regarding
> templating systems and storage formats, but most sites have
> standardized on the combination of Django and Markdown.  Talk
> to infra if you would like to use the CMS in this or some other
> fashion, we'll see what we can do.
> NOTE: the policy for dist/ dirs for managing project releases is
> similar.  We have setup a dedicated svn server for handling this,
> please contact infra when you are ready to start using it.
> [0]:
> [1]:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message