Frank Lichtenheld wrote: > A question that I have: For the sarge release I devised this > somewhat crude wml hack <if-stable-release> that enables us to > include content in the wml files and have it magically appear > once releases/info is changed for the release. This has the > advantage that it is really easy for all contributors to > understand and work with. It is somewhat limited though, especially > you can't stage the changes to e.g. releases/info itself. I like the <if-stable-release> tag because it makes it easy to grep for parts of the web site that vary between releases, inheriting that information from past releases. > Now I was wondering wether people think it would be worth > the additional complexity to set up an etch CVS branch for > this staging. I'm cautious about using CVS for branching, it's by far the hardest RCS to do merging with. I would prefer not to be put in a position of hand-merging conflicting changes right as we were trying to announce a release. (Of course, I'd also be happy to see webwml move to any more modern RCS that can support the current usage patterns well. It's the last thing I have to use cvs for, and one of the few remaining reasons to keep cvs.debian.org around at all. It'd be great to not have the security exposure and special-casing of cvs.debian.org any longer.) -- see shy jo
Attachment:
signature.asc
Description: Digital signature