> 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. > I think it's a good and widely used practice.
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? Not really on my own ;-) Since the mapred merged into trunk isn't a release, the last release is 0.7.1 (so the web site is 0.7.1) When the mapred becomes a release (ie 0.8), the last release is 0.8 (web site should be 0.7.1) Finally if a 0.7.2 maintenance release is needed, the last release is still the 0.8 (so the web site should be 0.8) Does it make sense? Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
