How about versioning only the documentation (user guide, programmer's guide, BPEL compliance, javadoc) instead of the whole site? That way, we could have a documentation index that would include all versions of the documentation. We could do this by copying only the relevant documentation pages in the same space. The other pages are 'live' documents and I would rather have people always access the latest version from the website (e.g. homepage, roadmap, ...).
This option, like option 2 below, offers the advantage that we can go and patch/augment the documentation for past versions if need be. This is useful to document known bugs, limitations, etc. alex On 5/29/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
Hi guys, It's a good idea to check our full website for 1.0 in, so it can be retrieved in case of needs and also published at some different location later on when we'll be updating everything for the next release. So we can either: 1. Check it in the release branches -> looong checkout 2. Create a new site directory beside trunk, tags and branches to hold the different site versions (like site/1.0). I'd personally go for #2, any strong opposing opinion? Bike shed bait. Matthieu
