That is what you need to do, yes. Karl On Mon, Dec 10, 2012 at 5:30 AM, Oleg Kalnichevski <[email protected]> wrote: > Folks > > If any of you has any practical experience with migration to svnpubsub, > please confirm my understanding that the absolute minimum expected from > us to be considered compliant with the new guidelines is to ensure that > web site content (regardless of the content generation process or > technology) gets checked in to a SVN location within our project space > (svn.apache.org/repos/asf/httpcomponents) and that infra is informed of > that location. > > Am I missing anything important? > > Oleg > > -------- Forwarded Message -------- >> From: Daniel Shahaf <[email protected]> >> Reply-to: [email protected] >> To: [email protected] >> Cc: [email protected] >> Subject: Re: Mandatory svnpubsub migration by Jan 2013 >> Date: Wed, 6 Jun 2012 19:02:45 +0300 >> >> Reminder: all project sites must switch to svnpubsub by Jan 1, 2013. >> The CMS is based on svnpubsub, so switching to the CMS implies switching >> to svnpubsub (but not the other way around). >> >> The Reply-To is set; do not CC the pmcs@ alias on replies. >> >> Cheers, >> >> -- >> Apache Infrastructure >> >> Joe Schaefer wrote on Wed, Feb 08, 2012 at 04:26:48 -0800: >> > [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER >> > INQUIRIES TO [email protected]] >> > >> > 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. >> > >> > >> > HTH >> > >> > >> > [0]: http://www.apache.org/dev/cms >> > [1]: https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/ >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
