XMLReleaseNotes todo
build date: in the future

<Action>
Action
It would be a good idea to express the kind of action taken in order to accomplish a feature, via the 'action' attribute of the 'Feature' XML element.
detail: func enhance
{plugin}   [0.10.0]
<AntDeploy>   [0.17.0], [0.4.0]
Plugins
Ship the XSLT-plugins into the XRN Ant task, via the 'deploy' feature, so that it is easier to reuse it from the outside.
The first client is the CVS change log XSLT plugin.
detail: func
<API>
API
Think of exposing a Java (and then in other languages if easy) API, so as to easier XRN integration within other systems.
detail: tech
<blockInheritance>
Block summary inheritance.
As long as a (composition, dependencies, requirements) summary block is not overriden, re-use it.
It just needs to be decided whether the summaries should be cumulative as long as the inheritance is enabled...
detail: tech fix
asking: EMercier
<crossReference>
Cross-reference graphes
A nice feature would be to propose a plugin that generates cross-references graphes as far as the composition, dependencies, requirements are concerned.
detail: func enhance
asking: EMercier
<CSS>   [0.9.0], [0.6.6], [0.6.4], [0.6.0], [0.4.0]
CSS split
Think of spliting the CSS into two parts: the part that should not be customized because it is structural, and the customizable part that is up to the user preferences (my colors may not be yours ;-).
detail: tech
<FeatureType>
Feature characterization
Added the possibility to define another attribute of each 'Features/Feature' XML element, so as to provide some more valuable information.
detail: func
<format>
Other formats
The textual release notes format should be handled.
Why not using XSL-FO for that?
detail: func
<graph>   [0.18.2]
Graph
Provide a dependency, requirement, composition graph.
Use Graphviz, for instance.
detail: tech
<HTMLContent>   [0.5.1]
Layout XSLT customization
XSL: identify, build, reengineer the key points of the default XSL layout transformation so that it is much easier to override the default behaviour.
detail: tech
<JavaPlugin>
Java plugin
It is important to open the Ant XRN task by provide programmatical entry points via an API that can generate stuff when the rendering process is triggered.
This would make the framework more open, and provide a place where to use external plugins.
This would be made very simple: you have a Java interface to implement, and that will be automatically triggered by the Ant XRN task. In order to inidcate that you want to use it, you would just have to provide the FQN of the class implementation.
detail: tech enhance
asking: EMercier
<maven>   [0.10.0]
Maven integration
The task should be integrated as a plugin-goal within Maven.
detail: func enhance
<migrate>
Last change of the XRN XSD
When the XRN XSD schema has not changed but that the declared version of XRN used is not uptodate, there is no need to report a compatibility issue.
This message should be removed from the Ant XRN task runtime, when it is not relevant.
This forces to introduce the last version of the XRN framework that applied an XSD schema structural change.
detail: tech enhance
<multiComponent>
Multi-component
Provide the integration of multiple components, so that it is possible to make cross references between components release notes.
detail: func enhance
<newVersion>
New version bootstrapping
Provide a way to create a new version into the XRN release notes file.
This will be achieved by the Ant XRN task.
detail: tech technical
<plugin>   [0.10.0]
Plugin documentation
Think of defining an entry point in each plugin, so that it can easily be documented.
detail: func
<RSS>
RSS
Provide a RSS flow, so that it is possible to view all new releases.
detail: func enhance
<titleHeaderFooter>   [0.13.0]
Welcome page
Propose like in javadoc a welcome HTML page that will be integrated to the components summary page.
detail: func enhance
<versionDirection>
Component version expression
It would be a good idea would be to be able to express the component version regarding an upper bound (inclusive or not) or a lower bound (inclusive or not).
With thus, you would be able to express versions like 'V1.5+' or 'V1.6.1-'.
This is especially useful when you want to express a requirement, or a dependency on another component.
detail: func enhance
asking: EMercier
<XHTMLCompliant>
XHTML 1.0 Transitional compliant
The log that certifies that the generated HTML code is compliant to this standard should be added to the 'About' section.
The logo is accessible from http://validator.w3.org.
detail: tech enhance
<XRNLite>
XRN Lite
A simple XSL stylesheet should be generated and made available, so that it can be used directly on a XRN release notes file.
Thus, by just opening the file in a browser capable of processing XSLT, the release notes would be directly rendered.
This is very important because it enables to render the release notes without having to run any process!
detail: tech enhance
<XSLTModel>
Model XSLT
Provide a mode where only XML is being output via the inner model XSL transformations, so as to enable to use some individual filter per component (the versions filter, the type filter, whatever).
detail: tech enhance
It would also nice to be able to express that they are some compatibilites issues with previous versions.
detail: func
asking: EMercier
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
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
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
Solve the problem of the XSD file not living in the same directory as the release notes themselves.
detail: tech
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
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
The HTML transformation should be able to be made easily internationalisable.
detail: tech
Provide a documentation about the framework, on how to use it.
detail: tech
asking: EMercier
contributor: EMercier
Create a plugin that enables to express the validators of the different items, as a plug-in implementation.
detail: func
Provide an another actual release notes for the framework, and a tutorial release notes.
detail: tech
Website: add some explanation on the welcome page of the site.
detail: func
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
Think of potentially using the XPointer and XLink standard in order to point/include other XML stuff within the framework.
detail: tech
Think of defining non visible releases, because they are internal.
detail: tech
Feature cross-reference.
It would be nice if we could refer to another feature from another feature in a clean way.
detail: func enhance

Release notes generated by XMLReleaseNotes V0.19.2