|
0.3.1
build date: 2004.31.03
deliveryDate: 2004.31.03 |
This is a very tiny incrementation compared to the previous release.
| [func] | Added an an about page on the web-site. |
| [func] | The releases sorting is better thought. The need of a documentation is now needed. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
|
|
|
0.3.0
build date: 2004.03.30
deliveryDate: 2004.03.30 |
This is a version that can already be used as far as HTML transformation is concerned..
| [func] | Added the concept of visibility for each item, so that it is possible to filter when rendering into HTML, for instance. It is adviced to use a value that ranges from 0 to 4, 4 meaning that the item is the most visible. This is now possible through the 'visibilityThreshold' XSLT parameter. |
| [func] | 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... |
| [func] | 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. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
|
|
|
0.2.6
build date: 2004.03.26
deliveryDate: 2004.03.26 |
This is a version that presents a better HTML transformation.
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
|
|
|
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'.
| [func] | XMLReleaseNotes2HTML.xsl: you can now define the lower and upper limits of the versions for which the HTML is generated. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
|
|
|
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.
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
| 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.
| [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. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.2.2] | fake 1.0 | A fake component. |
|
|
|
0.2.2
build date: 2004.03.21
deliveryDate: 2004.03.21 |
| [tech] | 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.
asking: EM
contributor: EM
|
| [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. |
| [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. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
| This is just how to show that you may not inherit from the previous requirements. |
| [new]
[from 0.2.2] | fake 1.0 | A fake component. |
| 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...
| [tech] | 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.
contributor: EM
|
| [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. |
| [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. |
| Composition |
|
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
|
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
|
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
|
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.0.alpha] | Logic | This should all be very simple and logic: the override mechanism described in the previous first 'Component' 'Dependencies'-sub-element is the same for the requirements. |
|
[from 0.0.alpha] | Ant 1.4.1 | For the moment, I just intend to build an Ant integration because this very easy. |
|
[from 0.0.alpha] | Java 1.3 | And Ant needs a Java Virtual Machine to run. |
| 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. The principle is that the 'Release' XML element should be sorted from the latest to the oldest.
| [func] | I need to think a little more on how to enhance the framework, without going to fast: one thing by one!
asking: EM
|
| [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. |
| [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. |
| Composition |
| [new]
[from 0.0.beta] | AntDoc 0.8.f | I like my little handy tool. |
| [new]
[from 0.0.beta] | WedSitor 0.3.0 | This enables me to publish the site for the tool (not really a component, OK :-) |
| Dependencies |
| [new]
[from 0.0.beta] | XSD 1.1 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [new]
[from 0.0.beta] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| Requirements |
|
[from 0.0.alpha] | Logic | This should all be very simple and logic: the override mechanism described in the previous first 'Component' 'Dependencies'-sub-element is the same for the requirements. |
|
[from 0.0.alpha] | Ant 1.4.1 | For the moment, I just intend to build an Ant integration because this very easy. |
|
[from 0.0.alpha] | Java 1.3 | And Ant needs a Java Virtual Machine to run. |
|
|
|
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.
| [tech] | You can define a technical item, here specified through the 'type' attribute set to 'tech", as well as a person having asked for the technical Item.
asking: EM
|
| [func] | An item 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 items have a type enables to produce technical or functionnal graphical release notes. |
| [tech] | fixes bug '1'Whatever the type of the item (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. |
| [func] | This is even possible to tell the person who was in charge with the implementation of the item.
contributor: EM
|
| [func] |
You can specify more than one contributor.
contributor: EM,
|
| [func] |
Ant of course more than one person asking for a new feature, for instance.
asking: EM,
|
| Composition |
| [new]
[from 0.0.alpha] | AntDoc | It is possible to tell on what components source the component depends on. |
| [new]
[from 0.0.alpha] | WedSitor | When you specify a component it belongs to, you will be able to tell in every release, through the 'Release' XML element, what version it has been compiled with. |
| Dependencies |
| [new]
[from 0.0.alpha] | XSD | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obolete. |
| [new]
[from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [new]
[from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [new]
[from 0.0.alpha] | Logic | This should all be very simple and logic: the override mechanism described in the previous first 'Component' 'Dependencies'-sub-element is the same for the requirements. |
| [new]
[from 0.0.alpha] | Ant 1.4.1 | For the moment, I just intend to build an Ant integration because this very easy. |
| [new]
[from 0.0.alpha] | Java 1.3 | And Ant needs a Java Virtual Machine to run. |
|
|