Managing project documentation (release vs CVS versions) ?

2002-01-16 Thread Vincent Massol
Hi, I have always been pondering how to best manage the following. Should there be 2 web sites per project : one for the latest release (containing docs + javadoc corresponding to the latest release) and one for nightly builds (containing docs + javadocs corresponding to the latest code) ? When

Re: Managing project documentation (release vs CVS versions) ?

2002-01-16 Thread Peter Donald
The recomended solution for this is to use a branch. ie When you make a release you also branch at same instant. Then if you need to update the current web docs you modify them in the branch, then update the website (which is using last branch released). If you need to update the docs for the

RE: Managing project documentation (release vs CVS versions) ?

2002-01-16 Thread Vincent Massol
I should have thought about this ... stupid me ... Thanks. -Vincent -Original Message- From: Peter Donald [mailto:[EMAIL PROTECTED]] Sent: 16 January 2002 23:38 To: Jakarta General List Subject: Re: Managing project documentation (release vs CVS versions) ? The recomended

RE: Managing project documentation (release vs CVS versions) ?

2002-01-16 Thread Conor MacNeill
: Managing project documentation (release vs CVS versions) ? I should have thought about this ... stupid me ... Thanks. -Vincent -Original Message- From: Peter Donald [mailto:[EMAIL PROTECTED]] Sent: 16 January 2002 23:38 To: Jakarta General List Subject: Re: Managing project