Re: Mandatory svnpubsub migration by Jan 2013

Hello Infra!

At the logging project most sub projects commit generated html to svn.
Going live is a matter of "svn up". Guess there is no problem to use
svnpubsub.

But there is one component (the upcoming log4j 2.0) which has started
with mvn site deploy. Is there a recommendation how combine this with
svnpubsub? The idea was to deploy to a local folder which is then
committed to svn. This would probably mean that a log4j2.0 website
update does mean a huge commit because most sources might be touched.
Is it a problem?

Cheers,
Christian

On Wed, Feb 8, 2012 at 1:26 PM, Joe Schaefer <joe_schaefer <at> yahoo.com> wrote:
> [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
> INQUIRIES TO infrastructure <at> apache.org]
>
> 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 http://www.apache.org/dev/project-site.html#svnpubsub
> 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,