Oh and Dave, while this won't be a well-documented feature of the CMS, whenever you are dealing with
a massive changeset that you know is ok and don't want to be bothered waiting for the CMS to generate a massive diff file to review, simply visit https://cms.apache.org/ooo-site/lazy_publish and hit submit- it's an O(1) server operation and there are no delays waiting for data to transfer between the cms host and the svn server. A word of caution is to not do this for other sites in the CMS as you may wind up seriously breaking them, but forooo-site there's no reason not to. HTH >________________________________ > From: Joe Schaefer <[email protected]> >To: "[email protected]" <[email protected]>; >"[email protected]" <[email protected]> >Sent: Tuesday, February 21, 2012 10:35 PM >Subject: Re: svn commit: r805698 - /websites/production/ooo-site/ > >So with Daniel's advice I've beefed up the >performance of the publish operation so it >mostly now just does a copy of staging instead >of a merge. Enjoy. > > > > >>________________________________ >> From: "[email protected]" <[email protected]> >>To: [email protected] >>Sent: Tuesday, February 21, 2012 10:33 PM >>Subject: svn commit: r805698 - /websites/production/ooo-site/ >> >>Author: joes >>Date: Wed Feb 22 03:33:58 2012 >>New Revision: 805698 >> >>Log: >>Lazy publish ooo-site >> >>Added: >> websites/production/ooo-site/ >> - copied from r805697, websites/staging/ooo-site/trunk/ >> >> >> >> > >
