Piotr Kosiorowski wrote:
Should we have version independent site -> always modified in trunk?
Or should we think about having a site (eg. JavaDocs, tutorial etc)
versioned and available for all versions at the same time?
The practice I've followed is to have the website reflect the latest
released version. Documentation for older releases can be found by
downloading those releases. Unreleased versions tend not to have good
documentation.
If the trunk diverges from the current release, and we need to update
the website, then we can use 'svn switch' on the web server to point the
website at the current release. Right now the trunk
(documentation-wise) still matches the current release 0.7.1, so this is
not an issue. But, if we merge mapred into trunk and then wish to make
a 0.7.2 release, then we might need to switch the web server to
branch-0.7. Does this sound reasonable?
Doug
