The following table shows the history of XMLReleaseNotes release notes.

VersionContentDelivery
0.2.5
build date: 2004.03.21
deliveryDate: 2004.03.21
Added the opportunity to use a CSS when transforming into HTML via the 'XMLReleaseNotes2HTML.xsl'.

  1. type = 'func'



    XMLReleaseNotes2HTML.xsl: you can now define the lower and upper limits of the versions for which the HTML is generated.
0.2.4
build date: 2004.03.21
deliveryDate: 2004.03.21
There is no new delivery, only the web site generation has changed and contains the internal AntDoc.

No delivery
0.2.3
build date: 2004.03.21
deliveryDate: 2004.03.21
This is patch and the top-child 'Deliveries' XML element has been adde so as to enable to express the delivery root URL.

  1. type = 'func'



    Added the opportuniy to add a 'ReleaseNotes' 'Deliveries' direct child that can specify the common HTTP URL (via the 'href' attribute) where the deliveries are gathered.
0.2.2
build date: 2004.03.21
deliveryDate: 2004.03.21

  1. type = 'tech'

    contributor list:
    • EM


    It would be nice and much more helpful if the HTML file output by the XMLReleaseNotes2HTML.xsl were able to only produce an HTML content (so as to integrate it into a HTML header page), or a complete HTML page.
  2. type = 'tech'



    The previous XSLT should also be able to be imported from other XSLT sources, so that the transformation can be used inline in other transformation, like those which produce HTML pages.
  3. type = 'tech'



    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.
The V0.2.0 and V0.2.1 were not OK, as far as the automatic delivery process is concerned.
0.2.0
build date: 2004.03.21
deliveryDate: 2004.03.21
This should be the very first release of the tool...

  1. type = 'tech'

    contributor list:
    • EM


    It would be nice and much more helpful if the HTML file output by the XMLReleaseNotes2HTML.xsl were able to only produce an HTML content (so as to integrate it into a HTML header page), or a complete HTML page.
  2. type = 'tech'



    The previous XSLT should also be able to be imported from other XSLT sources, so that the transformation can be used inline in other transformation, like those which produce HTML pages.
  3. type = 'tech'



    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.
This is still a very basic release, just made of two files: the XSD XMLReleaseNotes.xsd and an XML release notes example, XMLReleaseNotes.xml. It also includes the XSLT transformation XMLReleaseNotes2HTML.xsl.No delivery
0.0.beta
build date: 2004.03.18
deliveryDate: never
This is a bit more elaborate version, since new ideas have come to my mind, and this is the reason why I make a 'todo' release in order to express them.

  1. type = 'func'
    asking person list:
    • EM



    I need to think a little more on how to enhance the framework, without going to fast: one thing by one!
  2. type = 'tech'



    The first thing that I will on is a precise XSD, so that you can use tools that transforms the XSD into a Graphical User Interface like JAXFront in order to type the release notes.
  3. type = 'tech'



    The next step is to write an XSLT than nicely turns the XML release notes into HTML, so as to be able to publish it gently.
0.0.alpha
build date: 2004.03.18
deliveryDate: never
This version is a first try to build a tiny XML release notes framework. The summary provides an overall explaination of what the release is made of, what it consists of.

  1. type = 'tech'
    asking person list:
    • EM



    You can define a technical token, here specifie through the 'type' attribute set to 'tech", as well as a person having asked for the technical token.
  2. type = 'func'



    A token is a global concept that enables to identify a modification in the code, the way of building the component, or in the behaviour of the component. The fact that tokens have a type enables to produce technical or functionnal graphical release notes.
  3. type = 'tech'


    fixes bug '1'
    Whatever the type of the token (technical or functional), it may be specified as fixing a bug. This can bevery helpful when you already use a (web) bug tracker. We did not provide information on who was responsible for fixing the bug, because we think that it is this framework job.
  4. type = 'func'

    contributor list:
    • EM


    This is even possible to tell the person who was in charge with the implementation of the token.
  5. type = 'func'

    contributor list:
    • EM
    • TD


    You can specify more than one contributor.
  6. type = 'func'
    asking person list:
    • EM
    • TD



    Ant of course more than one person asking for a new feature, for instance.

Release notes generated by XMLReleaseNotes