> > Will it be and at what address would the staging website be visible at? > > None, unless you checkout site/staging to some web server at localhost. > Is that a problem?
No :-) Although it is safest to cast a vote against one published staging url. > > Will this mean that updates to tiles.apache.org can only be done via > > releases? > [snip] > maven-scm-publish-plugin works by checking out the current site into a > local directory, copying the new files into that location, and > committing again. It doesn't remove anything as far as I can tell. I can see using maven-scm-publish-plugin outside of the release cycle often useful. For example the patch from Michael re "wildcards documentation" i plan to commit (it makes sense to wait until svnpubsub is in place). I don't see the need for a release of tiles framework just to see it go to staging and then publish? But the maven generated sites list the version number at the top of the page, eg > Last Published: 2012-07-11 | Version: 3.0.1 and manually generating the site and pushing wildcard.html into site/staging/ means this header becomes "3.1-SNAPSHOT". Ugly. In some cases documentation must wait until a release is made, ie that documentation depends on new features yet to be released. Here everything just falls into the release process. In other cases, like "wildcards documentation", documentation enhancements come in that can be pushed immediately to staging. my question what is best practice here? The way i see it must be done seems rather clumsy… 1) checkout ^/framework/tags/tiles-parent-3.0.1/ 2) svn merge -rXXX ^/framework/trunk/src/site/apt/tutorial/advancedwildcard.apt 3) mvn site:site 4) cp target/site/tutorial/advanced/wildcard.html ../site/staging/framework/tutorial/advanced/wildcard.html 4a) hack the snapshot header back to the release version 5) svn ci ../site/staging/framework/tutorial/advanced/wildcard.html 6) cast vote ~mck -- "Although the Buddhists will tell you that desire is the root of suffering, my personal experience leads me to point the finger at system administration." Philip Greenspun | http://github.com/finn-no | http://tech.finn.no |
signature.asc
Description: This is a digitally signed message part
