On 11/04/2010 07:25 PM, Marnie McCormack wrote:
I'm not sure who is more confused now - I'm using oyxgen and have (of
course, doh) checked the docbook output locally before committing.
OK, I misunderstood. Sorry for reading the wrong thing into what you wrote.
But in order to get the stuff through the make and onto the website, there's
more beyond that - I've created the docbook for the new how-to and edited
the master book to add the entry for the new sub doc.
Are we really saying that there should be ?3 manual steps to get the docbook
onto our website for every new doc ?
I can add a web-publish target that handles the last two steps (in place
of scripts I use for that on my local box). But that only helps Linux users.
Are these the two steps you are thinking of?
(1) copying the built files to http://svn.apache.org/viewvc/qpid/site/
(2) svn commit from the qpid/site directory
I can automate copying the built files to the site directory and
launching the svn commit. I'd like the user to confirm the commit before
it gets published, though.
I think there are two issues:
(1) How does a Windows user publish to the web site?
You can do this now by copying the built files and svn committing them.
I am adding the target I described above to the make file, but that
doesn't work for Windows users.
(2) Should we automate publishing from the sources?
Sure, this makes sense. I'm gone next week and can't look into it today.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
