There are still a couple of outstanding JIRA issues that need resolved before we can go live. If anyone thinks of anything else that needs to happen, please add it to JIRA.
The only thing I can think of is; Why is it better to check in the generated site to SVN at all?
Think about it for a second...
1. I check in something bad.
2. Many hours later it is checked out and put on to the web site.
3. I am sleeping by that time, and 'others' doesn't pay attention until a user of some kind get in touch.
4. Whoever intercepts the user notification, has to be pretty alert, and do;
- Figure out what is a decent version, of the xdocs source.
- Check that out.
- Revert/Merge that old stuff into the working copy.
- Rebuild the site.
- Copy that generation into the avalon/site 'branch'.
- Commit those changes.
Not exactly what I call simply 'Revert to an Old version'.
IMVHO, either
* Do the Maven style; Let the build tool handle the publishing directly into the site.
OR
* Having a server side list of 'site revisions', so that when the cron job checks out, it takes the 'last number' in that list, and one have to update such file manually when a new site has been generated.
Advantage of the first one is that I will have immediate feedback, and check that the stuff went on to the site correctly, i.e. sanity-check.
Advantage of the second, that it is very easy to revert to an older site, i.e. remove last line in the file.
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
