On Fri, Dec 22, 2006 at 05:38:52PM +0100, Vincent Hennebert wrote: > Guys, > > Reading the release notes page is a bit disappointing I think: > "Hey, they made a new release! Let's look at the changes: > ok, bug fixes and new features. > Hmmm, the behaviour may change from 0.20.5. > Arghhh, what's that whole list of issues!!" > > I doubt any normal user will have a look at the detailed changes (I'm > not saying the changes page is useless!).
I agree. Note that the forrest sitemap.xmap contains a rule for releaseNotes.xml and a stylesheet releaseNotes2document.xsl to generate that from the status.xml document (i.e. the change list). Maybe it would be a good idea to reinstate that document and relegate the known issues to a separate document? But it should be possible to have a separately written introduction and a list of important changes above the transformed list of changes. > What about listing the major improvements in the new release? The things > that will catch the eye of the normal user? > I've attached a small patch to relnotes.xml, so you see what I mean. Good points. Simon > Index: relnotes.xml > =================================================================== > --- relnotes.xml (r??vision 489680) > +++ relnotes.xml (copie de travail) > @@ -34,7 +34,13 @@ > </li> > <li> > This release again contains many bug fixes and new features. See > - the <a href="changes.html">changes file</a> for details. > + the <a href="changes.html">changes file</a> for details. Most important > + changes: > + <ul> > + <li>basic support for OpenType fonts</li> > + <li>copy/paste from PDF files is now working</li> > + <li>support for cmyk colors</li> > + </ul> > </li> > <li> > See the <a href="compliance.html">compliance page</a> for an -- Simon Pepping home page: http://www.leverkruid.eu
