On Tue, 2003-10-28 at 06:00, Leo Simons wrote: > Farr, Aaron wrote: > > worry about deployment (still want to use the > > cvs update cron job?). > > I suggest just biting the bullet and doing
<snip/> > 3) generate all the new content and put it in avalon-site/site, then do > a really big 'cvs import' If we're going to keep using avalon-site/site (as opposed to something like target/docs), then we should update the maven build.properties. We'll keep the current src/ directory though right? > that, or doing a lot of 'cvs remove' and retrying dozens of times to > deal with lost connections and similar stuff, then doing lots of 'cvs > add' since 'cvs import' will not work. agreed. > > Should we get a vote before this goes live? It's a > > pretty significant change. > > nope. The doc policy: commit first, ask questions later. It should be > pretty clear to everyone that a change is underway :D If not, it will be clear very soon. :) > If you wanna go the above route, I need to do #1; I'm also happy to do > #2-#5. Just holler. > I still haven't finished all the docbook -> xdoc conversion, so unless someone else has, we'll need to either regenerate the content from the current src or finish the conversion before we're ready. The next step after this will be updating the individual projects to use maven's xdoc features. But this isn't necessary for the first release of the new site. -- jaaron <http://jadetower.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
