logging-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject Re: Mandatory svnpubsub migration by Jan 2013
Date Thu, 09 Feb 2012 13:36:31 GMT
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

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?


On Wed, Feb 8, 2012 at 1:26 PM, Joe Schaefer <joe_schaefer@yahoo.com> wrote:
> INQUIRIES TO infrastructure@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,
> 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]: http://www.apache.org/dev/cms
> [1]: https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/


View raw message