On 24 April 2013 05:28, Henri Yandell <[email protected]> wrote: > So if you're using the SVN approach, you check locally, then commit and go > hit publish on the CMS? > > If you commit to the source, I think that automatically does the build and updates the staging site.
You can then check the staging site before hitting publish. Perhaps try this out with a trivial change. However, given that the same staging site is shared by everyone, anyone else making updates at the same time will publish your changes if you have not yet done so. Publication copies the entire staging site across to live. Also it's not possible to drop the staging site except by reverting the original commit. So I suggest reviewing major changes locally first. The CMS system is very convenient for minor edits; typos and the like. > Hen > > On Tue, Apr 23, 2013 at 11:50 AM, sebb <[email protected]> wrote: > > > On 23 April 2013 19:25, Henri Yandell <[email protected]> wrote: > > > > > Looking at the site building docs, I could see how to modify the site > > > (install a CMS plugin or just modify SVN and test locally, I went with > > the > > > latter). My commit was then built by the buildbot. > > > > > > Where is the staging site to look at the buildbot output so I can then > be > > > happy pressing Publish? I couldn't see anything in the docs or the > > buildbot > > > that seemed to link to such a thing. > > > > > > > > If you use the CMS bookmarklet (it's not a plugin) it's one of the links > > shown at the top of the page when you commit. > > The link is to a protected private directory - e.g. [1] however that > > redirects to a shared directory [2] > > > > The ASF CMS docs could be updated with this info somewhere suitable. > > > > [1] > > > > > https://cms.apache.org/commons/wc/edit/sebb-{ramdomtag}/trunk/content/xdoc/releases/prepare.xml?action=staged > > [2] http://commons.staging.apache.org/releases/prepare.html > > > > Hen > > > > > >
