VersionContentDelivery
latest-built the 'never' and delivered the 'in the future' This enables to express what should be present in the release. The 'latest' version value is also a keyword.
todo-built the '2004.03.18' and delivered the 'in the future' This 'todo' version enables to express new ideas concerning the development. It would be a special keyword.
  1. type = 'func'
    asking person list:
    • EM



    It would also nice to be able to express that they are some compatibilites issues with previous versions.
  2. type = 'tech'



    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.
  3. type = 'tech'



    It is important to be able to split the release notes into several parts (files), so that multiple actors can write on it witout inter-blocking on the same resource.
  4. type = 'func'



    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...
  5. type = 'tech'



    Solve the problem of the XSD file not living in the same directory as the release notes themselves.
  6. type = 'tech'



    Outputs some CSS classes in the HTML file got from the XMLReleaseNotes.xsl XSLT transformation, so that you can easily provide your own CSS.
  7. type = '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).
  8. type = 'func'



    It is interesting that the release notes may enable to express what versions are being used, their state, in what locations it is being used, what version is used in what location.
  9. type = 'tech'



    The HTML transformation should be able to be made easily internationalisable.
It would be nice if you could provide a global message that provides some information about the deliveries, as an explanation on the format, and how use the bundle.
0.2.0-built the '2004.03.21' and delivered the '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.
0.0.beta-built the '2004.03.18' and delivered the 'never' This is a bit more elaborate version, since new ideas have com 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.
  • Depending on the version, you do not necessarily have the same number of artefacts.
0.0.alpha-built the '2004.03.18' and delivered the '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.
  • This enables you to tell where to get the release.
  • This deliveries section can be composed by multiple artifacts, for a client and a server side package for instance.
Release notes generated by XMLReleaseNotes