Features of component
XMLReleaseNotes

  [todo]
It would also nice to be able to express that they are some compatibilites issues with previous versions.
detail: func
asking: EMercier
  [todo]
A good idea would be to create a new Plone product that would enable to fulfill the release notes, so that it is possible to make developers enter their release notes as they are developing.
detail: tech
  [todo]
It is important to be able to split the XML release notes file into several parts (files), so that multiple actors can write on it without inter-blocking on the same resource.
detail: tech
  [todo]
Why not enabling the releasers to express the content of the release? Maybe, this would go too far, and this not make this framework just a release notes tool. This is not a packaging tool, but plugins could be considered all the same...
detail: func
  [todo]
Solve the problem of the XSD file not living in the same directory as the release notes themselves.
detail: tech
  [todo]
Very important thing: it would be very helpful to propose an XSLT that turns the XML release notes files into OpenOffice XML format, so that you can then transform the information as you want to (PDF, MS Word, HTML). It would be necessary to write an OpenOffice auto-conversion macro.
detail: tech
  [todo]
It is interesting that the release notes may enable to express what versions are being used, their state, in what locations they are being used, what version is used in what location.
detail: func
  [todo]
The HTML transformation should be able to be made easily internationalisable.
detail: tech
  [todo]
Provide a documentation about the framework, on how to use it.
detail: tech
asking: EMercier
contributor: EMercier
  [todo]
Create a plugin that enables to express the validators of the different items, as a plug-in implementation.
detail: func
  [todo]
Provide an another actual release notes for the framework, and a tutorial release notes.
detail: tech
  [todo]
Website: add some explanation on the welcome page of the site.
detail: func
  [todo]
XMLReleaseNotes2HTML.xsl: provide and use icons. Do not hypelink the text of a 'Deliveries/Delivery' XML element, but just the delivery package itself.
detail: tech
  [todo]
Think of potentially using the XPointer and XLink standard in order to point/include other XML stuff within the framework.
detail: tech
  [todo]
Think of defining non visible releases, because they are internal.
detail: tech
Feature cross-reference.   [todo]
It would be nice if we could refer to another feature from another feature in a clean way.
detail: func enhance
Delivery section   [0.18.1]
The rendered HTML pages used to contain 'No delivery' section when no delivery is present for a given version.
This has been removed since it polutes the rendering.
detail: func fix
contributor: EMercier
Content rendering   [0.18.0]
When some content was expressed using a <![CDATA[]]> statement, the content was rendered as is, instead of considering the HTML tags.
This is now fixed?
But this introduces the relevance of the 'contentType' attribute, which should be rather used to indicate whether the textual content should be interpreted or not instead...
detail: tech fix
contributor: EMercier
Components ordering   [0.17.1]
When generating multi-components release notes, the sorting of the components now depends on the component identifier.
detail: func fix
Actors XSD and migration   [0.15.0]
Added the 'XRNActors.xsd' schema in order to know how to fulfill the actors XML file.
Fixed the 0.13.0 to 0.14.0 migration stylesheet.
detail: tech fix
Release build date   [0.15.0]
The release build date has been added to the summary page when the multi-component feature is being used.
detail: func enhance
Bottom banner visibility   [0.10.1]
The bottom banner for XRN promotion was still visible on the generated HTML pages (with multi-components enabled), even when the 'banner' Ant attribute was set to 'no'.
detail: tech bug-fixing fix
Feature 'ID' attribute   [0.5.1]
Made this 'Feature/@ID' attribute a string, so that mnemonics may be used.
detail: func
Abstract   [0.5.0]
Provided the opportunity to define an abstract for each feature, through an 'Abstract' element within the 'Features/Feature' XML element: this enables to name the feature shortly.
detail: func
  [0.4.1]
Fixed the bug of the delivery download hyperlink that was wrong.
detail: tech bug-fixing
  [0.4.1]
XSL: enable to remove the default banner at the bottom via a 'banner' parameter. Don' disable it, otherwise the tool won't be known and there will be little support and enhancements.
detail: tech
  [0.4.1]
Fixed the release which missed the release notes! How possible is it?
detail: tech fix
  [0.4.0]
XSL: turned the 'standAloneHTML' parameter default value to 'false'.
detail: tech
  [0.4.0]
Fixed the bug concerning the 'Requirements', 'Dependencies' and 'Composition' display, which were not always present as required.
detail: tech bug-fixing
  [0.4.0]
Made the 'Release/@deliveryDate' optional, because you can build releases without never spreading them!
detail: func
  [0.4.0]
XSD: the schema now belongs to the 'http://xmlreleasenotes.free.fr' target namespace, which should be refered as 'xrn'.
detail: tech
  [0.3.3]
Replaced the term 'item' by 'feature' because it is more appropriate.
Added the 'BuildingBlock' within the 'Feature' element, in order not mix the complex element with text.
detail: tech
  [0.3.3]
Added the opportunity to define a release builder via the 'builderID' attribute on the 'Release' element.
detail: func
  [0.3.3]
XMLReleaseNotes2HTML.xsl: added the 'delivery' parameter that enables not to output de "Delivery" column, which enables to download the artefacts.
detail: func
  [0.3.1]
Added an an about page on the web-site.
detail: func
  [0.3.1]
The releases sorting is better thought. The need of a documentation is now needed.
detail: func
  [0.3.0]
Now, enables to tell whether the dependencies and requirements should be inherited from the previous versions. How does it work? For each 'Release' XML element...
detail: func
  [0.3.0]
XMLReleaseNotes2HTML.xsl: added the possibility to filter the type of items to be documented through the 'typeFilter' parameter. This enable to remove for instance the technical information into a functional release notes dedicated to end-users.
detail: func
  [0.2.5]
XMLReleaseNotes2HTML.xsl: you can now define the lower and upper limits of the versions for which the HTML is generated.
detail: func
  [0.2.3]
Added the opportuniy to add a 'ReleaseNotes' 'Deliveries' XML element direct child that can specify the common HTTP URL (via the 'href' attribute) where the deliveries are gathered.
detail: func
  [0.2.0]
The architecture and files of the projets are now OK; the resources are under CVS and all the delivery engine should work, through an Ant buildfile.
detail: tech