Currently we have a 1.2.5 build that has no details of whats changed in the documentation thats included with it. The problem with the way release notes currently work is that the release-notes.xml contains the current release - but since a new build (like 1.2.5) is created before its voted on whether to *release* it then theres a catch 22 situation.
I'd like to change the release-notes.xml so that its just and index page with links to the various release notes for the different versions - that way we could have created a release-notes-1.2.5.xml document and had a link to it and distributed them with the build. Also if we did it that way, then we could build up the release notes as changes are made, rather than having to mess around trying to identify whats happened since the last release. Any objections to this - or alternative proposals? Niall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
