site-publish/ has been removed, so you no longer need to build stuff locally and commit the results. You simply commit your changes, wait about a minute for the CMS to build them, and publish using the URL I mentioned or the publish.pl script on people.apache.org.
FWIW the CMS bookmarklet will work too on the incubator siteifyou prefer to use a browser for this purpose. >________________________________ > From: Rob Weir <robw...@apache.org> >To: general@incubator.apache.org >Sent: Monday, March 5, 2012 9:48 PM >Subject: Re: [SITE] CMS cutover for incubator site on Monday > >On Sat, Mar 3, 2012 at 10:39 AM, Joe Schaefer <joe_schae...@yahoo.com> wrote: >> I'll be cutting over the incubator site to >> svnpubsub based on the CMS this coming Monday. >> Please be advised this will impact the workflow >> for publishing stuff: instead of committing build >> output to site-publish and svn upping the tree >> on people.apache.org, you will instead publish >> your changes by either visiting >> >> https://cms.apache.org/incubator/publish >> >> or by using the publish.pl script on people.apache.org. > >So for the podling status files, we currently do this: > >http://incubator.apache.org/openofficeorg/ppmc-faqs.html#status > >So, we edit the XML, ant, svn commit the changed XML and generated >HTML, then go to people.apache.org and svn update. > >Does this just change the last step, so instead of an svn update on >people.apache.org we do the publish script? Or something else? > >-Rob > > >> Please read up on CMS usage at >> >> http://www.apache.org/dev/cms >> http://www.apache.org/dev/cmsref >> >> Thanks for your attention! > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > > > >
