+1 to all items. -Vincent
> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 19 September 2003 00:44 > To: 'Maven Developers List' > Subject: RE: Several web site versions in CVS > > > > - I don't think it's normal to store history data in CVS. A SCM is > > > meant to do that for you. I won't save several versions of the same > > > file so why would I do this for web sites. > > > > So that users with old versions can go look up the old > > documentation, e.g. > > in Maven's case, > > beta 10 users can look at the install docs and we can update them for > > 1.0-rc1 as we go. > > > > But how big will CVS checkouts and the doco distribution be when we > release > Maven 2010? :) > > I'll summarise the parts of the thread I'm +0.75 on (strongly in favour, > willing to work on it, just not right now :) > - only latest version in CVS, use CVS for history > - deploy multiple versions to web server > - top level version on web site is last release, not current CVS > - link certain docs through to current CVS (eg FAQ, news and status) > > I think this can be achieved by doing the following: > - change siteDirectory to > /www/maven.apache.org/releases/${pom.currentVersion} > - when making an actual release, do another site:deploy, but: > A) change some links like the FAQ and news and status to point to > /SNAPSHOT/... > B) deploy to /www/maven.apache.org instead of the other > - when releasing a site from CVS, pom.currentVersion ends in -SNAPSHOT, so > deploy to /SNAPSHOT/ instead > > This way, historical docs keep their own FAQ and news and status, live > site > points to the latest of them, but current release of all else. > > Sound ok? > > Cheers, > Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
