|
start date:
2005.02.05
build date:
2005.03.21
builder:
EMercier
XRNActorsModel XSLT model
Added the 'expandActorName' parameter that indicates whether the actor identifiers ('ID' attribute) should be expanded against their display name, when available in the actors XML files.
Added the 'equalizeCase' parameter that indicates whether the actor identifiers should be all equalized as far as the case is concerned (in lower case). This solves the problem of the same actor being entered with various cases, and thus not being recognized as the same actor.
detail:
tech
enhance
XSD
asking:
contributor:
|
|
Dependencies and requirement blocks
The way the dependencies and requirements blocks have been widely revisited. The composition block has not bee touched.
It is now possible to indicate a range (with or without an lower or upper bound) of versions, an excluded precise version, in order to indicate the components a component depends on, or what components it requires.
detail:
func
enhance
asking:
contributor:
|
Asking persons and contributors
The 'askingPersonID' and 'contributorID' attributes of the 'Feature' element have been removed, because they are duplicated regarding the inner 'AskingPersons' and 'Contributors' XML nodes.
detail:
func
enhance
asking:
contributor:
|
|
|
Composition
|
| from
0.18.0
|
XRNGuide 1.0 |
This guide is supposed to explain what the XRN framework is about, and how to use it. |
|
Dependencies
|
| from
0.18.2
|
standard
|
When working on the 'org.xrn.plugin.impl.Graph' XRN Java plug-in. |
| from
0.18.2
|
software
|
When working on the 'org.xrn.plugin.impl.Graph' XRN Java plug-in. |
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| from
0.18.2
|
standard
|
When the 'org.xrn.plugin.impl.Graph' XRN Java plug-in is used. This is part of the JWSDP package provided by Sun. The required jar file are 'jaxb-api.jar', 'jaxb-impl.jar', 'jaxb-libs.jar', 'jaxb-xjc.jar', 'jax-qname.jar', 'namespace.jar', 'xsdlib.jar'. |
| from
0.18.2
|
software
|
When the 'org.xrn.plugin.impl.Graph' XRN Java plug-in is used. This project contains the famous 'dot' executable, which is required in this case. This component is responsible for generating the graphs. Earlier versions has not been tested. |
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
|
start date:
2005.01.04
build date:
2005.01.31
builder:
EMercier
The fight with the Java classloaders should be over now.
Class loaders
Because of a misuse of the Java class loader, there were strange problem at runtime with the XSLT and the JAXB.
detail:
tech
fix
asking:
contributor:
|
|
Actors graph
A first XRN Java plug-in in proposed in early alpha version. Its implementation class is 'org.xrn.plugin.impl.Graph'.
It generates - via the Dot component - a graph per actor, that displays the relationship his relationships with all components (as a builder, asking person, contributor).
More explanation to come, since this is still experimental.
detail:
func
enhance
asking:
contributor:
|
|
Java plug-in
The Java plug-in feature is delivered as very alpha.
This feature enables to open the framework by proposing additional views on the pieces of information present in the release notes.
Plug-in should be asked by end-users, developed by developers and used when running the Ant XRN task and set the parameters that enable to use the plug-in.
On that purpose, the inner 'javaPlugin' XML element has been added to the XRN task. This is a derivation from the Ant built-in 'Path' core element. Moreveover, its mandatory 'classFQN' attribute enables to indicate the Fully Qualified Name of the class that implements a plug-in.
detail:
func
enhance
asking:
contributor:
|
|
XSD 'Item' element
The 'Feature/Item' XML element count can now be null, provided you provide at least a 'Title' sibling element.
This enables to define features, just by their title, which should be used with wisdom.
detail:
func
business
asking:
contributor:
|
|
|
Composition
|
| from
0.18.0
|
XRNGuide 1.0 |
This guide is supposed to explain what the XRN framework is about, and how to use it. |
|
Dependencies
|
| new |
standard
|
When working on the 'org.xrn.plugin.impl.Graph' XRN Java plug-in. |
| new |
software
|
When working on the 'org.xrn.plugin.impl.Graph' XRN Java plug-in. |
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| new |
standard
|
When the 'org.xrn.plugin.impl.Graph' XRN Java plug-in is used. This is part of the JWSDP package provided by Sun. The required jar file are 'jaxb-api.jar', 'jaxb-impl.jar', 'jaxb-libs.jar', 'jaxb-xjc.jar', 'jax-qname.jar', 'namespace.jar', 'xsdlib.jar'. |
| new |
software
|
When the 'org.xrn.plugin.impl.Graph' XRN Java plug-in is used. This project contains the famous 'dot' executable, which is required in this case. This component is responsible for generating the graphs. Earlier versions has not been tested. |
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
Deliveries
|
|
XMLReleaseNotes-0.18.2.zip
|
The 'XMLReleaseNotes.jar' library file now contains the 'XMLReleaseNotes.xsd' schema mapped into Java classes via the JAXB technology. |
|
|
start date:
2004.12.16
build date:
2004.01.04
builder:
EMercier
This version fixes numerous runtime issues with Ant and the JRE.
Summary plug-in layout
The plug-in layout has bee enhanced, so that it is now possible to generate HTML additional entries at the top level, that is to say for all components.
This is supposed to enable the development of pages that report information concerning all components present in a multi-release notes rendering.
detail:
func
enhance
asking:
contributor:
|
|
Runtime stability
This version should be much more flexibl as far as the runtime environment is concerned.
There used to be problem when the XRN task declaration made reference to jar files outside the Ant 'lib' directory.
This is the reason why the 'URIResolverPath' and 'XRNPath' features have been introduced.
detail:
tech
fix
asking:
contributor:
|
|
'SectionFilter' XSLT model plug-in
The plug-in has been fixed because it used to remove the 'Features' XML element in any case.
A 'showFeature' additional XSLT paramter has been introduced so as to be able to filter on the features as well.
detail:
tech
fix
asking:
contributor:
|
|
URI resolver path
Added the 'URIResolver' inner element to the Ant XRN task, so as to enable the Ant runtime to find the .xsl file present in the task jar.
This is only handy when you define the XRN task via a 'typedef/taskdef' and that the jar is not present under Ant 'lib' directory.
detail:
tech
technical
asking:
contributor:
|
|
Actors plug-in layout
This new plug-in layout takes benefit of the new plug-in layout extension at the level of the summary.
This is just a bootstrap and will be enhanced, but it provides an example.
The idea behind is to generate a kind of hall of fame of the actors involved in the process for a given component.
detail:
func
enhance
asking:
contributor:
|
|
XSLT Path
Addes the 'XSLTPath' inner XML element to the Ant XRN task, so as to enable Ant runtime to find the XSLT factory implementation to be loaded when it resides outside the 'lib' directory.
JRE V1.4 should not be concerned with that feature (since Xalan is shipped with the Java runtime) unless they intend to use another implementation that lives outside the 'Ant' lib directory.
detail:
tech
technical
asking:
contributor:
|
|
Delivery section
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
asking:
contributor:
|
|
|
Composition
|
| from
0.18.0
|
XRNGuide 1.0 |
This guide is supposed to explain what the XRN framework is about, and how to use it. |
|
Dependencies
|
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
|
start date:
2004.11.29
build date:
2004.12.15
The release notes of the XRN Guide and the XRN web site have been created.
XRN deploy via Ant
The Ant 'deploy' now also extracts the 'XMLReleaseNotesCommon.xsl' file.
This is necessary if someone intends to use the XSL machinery for integrating XRN into another HTML generation process.
detail:
tech
fix
asking:
contributor:
|
|
XML namespace
There were some unwished XML namespace references in the generated HTML stuff.
The generated HTML pages should now be XHTML 1.0 Transitional compliant.
detail:
tech
fix
asking:
contributor:
|
|
Ant XRN task package changed
The Ant XRN task has been moved from Java package 'org.ed.pack.xmlreleasenotes' to 'org.xrn.ant'.
Do not forget to change the task 'taskdef' declarations accordingly!
detail:
tech
enhance
asking:
contributor:
|
Ant XRN task declaration
You can now directly use the Ant XRN task by using a 'typedef', instead of a 'taskdef'.
The resource name is 'XMLReleaseNotes/org/xrn/ant/task.properties'.
detail:
tech
enhance
asking:
contributor:
|
|
The feature reason
The XSD 'why' attribute has been turned into a 'reason' attribute.
This is supposed to have been propagated to all the XRN core (CSS style sheet, XSL style sheets).
detail:
func
business
asking:
contributor:
|
|
Content rendering
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
asking:
contributor:
|
|
|
Composition
|
| The delivery now contains explicitely the XRN Guide. |
| new |
XRNGuide 1.0 |
This guide is supposed to explain what the XRN framework is about, and how to use it. |
|
Dependencies
|
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
|
start date:
2004.11.18
build date:
2004.11.27
The "XRN Guide" is still not complete, but it has been much enhanced. The web site has been reviewed, so that it should be clearer.
XRN Guide
The guide begins to be usable now...
detail:
func
business
asking:
contributor:
|
|
|
Dependencies
|
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
|
start date:
2004.11.15
build date:
2004.11.18
This is simply a release that proposes a guide, name the "XRN Guide". The web site has been enhanced, so as to integrate this guide.
XRN Guide
A guide has been started, so as to explain how to use the XRN framework, from an end-user perspective.
This is just starts and needs much, much work...
detail:
func
business
asking:
contributor:
|
|
|
Dependencies
|
| from
0.17.1
|
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| from
0.17.1
|
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| from
0.17.1
|
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| from
0.17.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| from
0.17.1
|
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
|
start date:
2004.11.10
build date:
2004.11.14
This release addresses bug fixings but above all the cross references plugin layout.
Plugin layout
Now, the 'XRN2HTMLPluginReference.xsl' plugin layout is fully functional.
detail:
func
enhance
asking:
contributor:
|
|
Block rendering
Fixed the composition, dependencies, requirements and deliveries blocks as far as the column widths are concerned.
detail:
func
fix
asking:
contributor:
|
|
Components ordering
When generating multi-components release notes, the sorting of the components now depends on the component identifier.
detail:
func
fix
asking:
contributor:
|
|
|
Dependencies
|
| new |
software
|
In order to compile the Ant Java source code. This is required because we want to work on fix version of Ant, so as to make sure that is actually Ant V1.5+ compatible. This Ant distribution also contains the necessary 'ant.jar' (for compiling with the Ant API), 'optional.jar' that is part of Ant (and which is required at compile time), and 'xml-apis.jar' libraries, so you do not need to bother. Just make sure that those libraries are intact, and actually those shipped with Ant V1.5.0! |
| new |
|
This is both a dependency and a requirement (at runtime). The Ant V1.5.0 'xercesImpl.jar' is used for compilation: it should however be present in your clean Ant V1.5.0 runtime, so that you do not have anything to do with it. |
| new |
software
|
In order to use all Ant new features as far as the process managment is concerned (use of the 'macrodef' task). This is required for development because the Ant buildfiles only support this (fresh, yes, too bad) version. |
|
Requirements
|
| Of course, you need the current XRN version of the Ant XRN task 'XMLReleaseNotes.lib' present in the 'lib' directory of the delivery package. The jar library file must be present in Ant runtime 'lib' directory. |
| new |
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. Note that the Ant runtime is supposed to contain in its 'lib' directory the shipped-with 'xercersImpl.jar' and 'xml-api.jar' libraries. |
| new |
|
You need to have an XSLT implementation library like Saxon V6 (download the jar here) or Xalan V2+ (download the jar here) in your Ant 'lib' directory. |
|
Deliveries
|
|
XMLReleaseNotes-0.17.1.zip
|
The 'XRN2HTMLPluginReference.xsl' plugin layout file is now present both in the zip delivery and in the Ant jar file. |
|
|
start date:
2004.10.30
build date:
2004.11.10
This is a dirty release (not much detailed and missing source code documentation). Added the concept of tags and added the multiple page plugin feature.
Contributor and asking person
Fixed the remaining bug due to the XML name change.
This used to prevent the multiple contributors and asking persons from appearing in the generated feature HTML pages.
detail:
tech
fix
asking:
contributor:
|
|
Ant 'deploy'
The feature was bugged (the 'deploy' Ant XRN task parameter) because the 'XMLActors.xsd' extraction was incorrect.
detail:
tech
fix
asking:
contributor:
|
|
Dependencies
Fixed a bug that used to make the generated XML not compliant with the framework.
detail:
tech
fix
asking:
contributor:
|
|
Plugin layout
Added the opportunity to extend the multiple page layout via some plugins.
This is possible via the 'pluginLayout' Ant task inner XML element.
detail:
func
enhance
asking:
contributor:
|
|
Tags
Added a new optional 'Tags' elements as a child element of the 'Feature' XML element.
This makes the framework more extensible because XSLT model plugin can take benefit of this extra information.
This new tag should also be deployed at other levels, like the 'Release', 'Component', for instance.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
start date:
2004.10.25
build date:
2004.10.25
The feature hierarchy concept has been introduced.
Parent feature
The 'Feature/@parentID' attribute has been added.
This enables to indicate that a feature belongs to a parent-feature, and thus provide a hierachy among the features.
Still beta and should be considered as a try...
detail:
func
business
asking:
contributor:
|
|
Features sum-up
The features hierarchy is now emphasized on the features summary page, by nesting the feature content with a parent within its parent.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
start date:
2004.10.24
build date:
2004.10.25
Some bugs have been fixed. Added new XSLT model plugins.
Dependencies
The new 'DependencyModel.xsl' new plugin enables to inline the release notes dependency-components of a component.
When a component has a new dependency (expressed via the 'Release/Dependencies/Component' XML element), this plugin inlines the depending-component by looking at its XRN release notes found via the corresponding 'ReleaseNotes/Components/Component/@xml' attribute.
This is the reason why it is important to express the XRN release notes of all depending components.
detail:
func
enhance
asking:
contributor:
|
|
Implicit migration
Added the 'implicitlyMigrate' parameter to the Ant task, so that it is possible to migrate the provided XRN files if necessary, without migrating the original.
No, when the Ant 'migrate' parameter is used, only the migration is performed.
detail:
func
enhance
asking:
contributor:
|
|
Section filter XSLT model
This new XSLT model 'SectionFilterModel' enables to filter the sections to keep when generating the release notes.
It enables to filter the 'Summary', 'Composition', 'Dependencies', 'Requirements' and 'Deliveries' XML 'Release'-child elements individually.
Usefull, for instance, when you want to generate an HTML download page.
detail:
tech
technical
asking:
contributor:
|
|
CVSModel XSLT model plugin
Fixed the deprecated 'Feature/Abstract' XML element use (which is now 'Feature/Title').
detail:
tech
fix
asking:
contributor:
|
|
Actors XSD and migration
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
asking:
contributor:
|
|
Release build date
The release build date has been added to the summary page when the multi-component feature is being used.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotes-0.15.0.zip
|
Added the previously forgottent 'XRNActors.xsd'. Added the XSLT model 'DependencyModel.xsl' and 'SectionFilterModel' plugins. Removed the 'DownloadLayout.xsl' XSLT layout, which is not used anymore. |
|
|
start date:
2004.09.01
build date:
2004.10.21
Miscellaneous features have been added.
Actors
The 'Actors.xsd' schema has been normalized and you can now use it in order to define all actors involved in the process.
Either you use the 'Actors' top-child XML element of 'ReleaseNotes', or you use the 'XRNActors' plugin model XSL in order to provide one.
The actors file should comply to the 'XRNActors.xsd' schema present in the package.
For every actor, when this plugin is used, you can directly write to him by clicking the hyperlink (via a 'mailto' HTML tag).
detail:
func
business
asking:
contributor:
|
|
Feature title
The 'Feature/Abstract' XML element has been renamed 'Title' because this is more adapted.
detail:
tech
fix
asking:
contributor:
|
|
Release 'freshness' indicator
On each HTML release, the "freshness" of the release is now indicated by a color at the right of the version name.
detail:
func
enhance
asking:
contributor:
|
|
XSD change
The inner 'Contributors' and 'AskingPersons' XML element now contain 'Actor' XML elements so as to simplify the XSD.
The 'Abstract' element has been renamed as 'Title'.
detail:
tech
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.31
A minor release with only the title header, footer new feature.
Cumulative
The 'cumulative' attribute of the Ant XRN task has been made obsolete.
The ''VersionAndTypeFilterModel' model XSLT plugin should be used instead.
detail:
tech
bug-fixing
fix
asking:
contributor:
|
|
Title, header, footer
You can now provide a title, a header and a footer for the multi-components into HTML.
This is possible in the Ant task through the inner 'title', 'header' and 'footer' XML elements.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.29
All the filtering has been replaced by a model XSLT. There are backward incompabilities.
Multiple asking persons and contributors
When the inner 'Contributors' and 'AskingPersons' XML element (in the 'Feature' XML element) were used, only the first actor was output in the HTML page.
detail:
tech
bug-fixing
fix
asking:
contributor:
|
|
Feature with no ID hyperlink
On the 'Feature' HTML page, add an hyperlink to the release where the anonymous feature has been defined.
detail:
func
bug-fixing
fix
asking:
contributor:
|
|
Filtering
The version (via the 'firstVersion' and 'lastVersion' attributes), feature type (via the 'type' attribute) and importance (via the 'importanceThreshold') filtering has been removed from the Ant XRN task.
Those filters are now performed by the ''VersionAndTypeFilterModel' plugin-model XSLT, in order to make the XSLT code easier.
detail:
tech
enhance
asking:
contributor:
|
|
Importance default level
The importance default value is now considered to be set to 3, so that it makes sense: it was set to 4, so that all features are equaly very important by default.
The level 5 has been added, so as to make 3 in the middle of the range.
detail:
tech
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.28
Added the 'Feature' summary HTML page, which enables to review all the release notes features.
Features HTML page
Provide an HTML page that gathers all features.
This is still beta and will be improved...
detail:
func
enhance
asking:
contributor:
|
Feature inheritance and layout
The layout of the feature has been enhanced.
Multiple features with the same 'ID' are now gathered.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.16
Minor enhancements.
Obsolete XRN file
The warning output when a XRN file is obsolete now states the ID of the component.
detail:
tech
enhance
asking:
contributor:
|
|
Bottom banner visibility
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
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.16
This is a major release since multiple-components release notes can be now be generated properly.
XSLT implementation
Provided the ability for the user to define the XSLT implementation to be used.
This is possible via the task attribute 'processor', which should be set to the class fully qualified name that implements the 'javax.xml.transform.TransformerFactory' interface.
detail:
tech
enhance
asking:
contributor:
|
|
Maven
Now provides an XSLT model for integrating the maven POM.
This is possible via the 'MavenModel' model XSLT plugin: the POM short description is just taken and integrated into the release notes.
detail:
func
enhance
asking:
contributor:
|
|
Multiple components
Added the opportunity to generate the release notes for more than one component at the same time.
The Ant task now supports the 'fileset' inner XML element.
Some navigation pages are now being generated when the feature is enabled.
The javadoc-like selectors have been added to the CSS.
Multiple HTML pages are being produced, a little bit like javadoc does, so as to split the different release (present the generated HTML generated by the XMLReleaseNotes2HTML.xsl a bit like javadoc format, so as to output a single HTML page for each release).
detail:
tech
enhance
asking:
contributor:
|
|
XSLT model plugin
It is now possible to use the model XSLT present in the jar via the Ant 'plugin' attribute that can be used on the 'model' XML inner element.
Refer to it as you would via the 'xsl' attribute, but omit the '.xsl' extension.
detail:
tech
asking:
contributor:
|
|
Component summary
A top-child XML element 'Summary' has been added so as to provide a way to briefly describe what the component is about.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.08.06
delivery date:
2004.08.06
New feature available: the download page generation. The CSS has been largely revisited.
CSS
Totally re-engineered the CSS, so that there are now only class selectors.
Began to annotate the selectors, so as to easier the customization.
detail:
tech
enhance
asking:
contributor:
|
|
Download page
It is now possible to generate a single download page that enabes to overview all the deliveries, while removing the feature details.
This is possible via the Ant 'downloadPage' new feature.
detail:
func
enhance
asking:
contributor:
|
|
Feature importance
Fixed the feature importance bug that was actually not taken into account during the XSLT.
detail:
tech
bug-fixing
fix
asking:
contributor:
|
|
Icons
Prepared the XSL so that icons may be included in the generated HTML page, so as to enhance the layout.
detail:
tech
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.8.0
|
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.8.0
|
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.07.23
delivery date:
2004.07.23
A major release because it brings the release notes cross-references feature, as well as the XML release notes validation.
Cumulative
Now, provides an additional XSLT model that enables to generate a release notes between two versions, in a cumulative way.
Ant: the 'cumulative' attribute has been added in order to ask for a cumulative release notes.
detail:
func
enhance
asking:
contributor:
|
|
Implicit migration
An implicit migration before the rendering is performed on the release notes when required, without overwritting the file (done in memory only).
detail:
tech
enhance
asking:
contributor:
|
|
Validation
It is now possible to check that the structure of the data entered in the XRN release notes XSML file are compliant with the framework.
It is now posible to check the XRN release notes XML file against its XSD schema (present in the jar).
This can be achieved via the Ant task by using the 'checkValidity' top parameter.
Now, an additional feature would be to actually analyze the XRN release notes file in order to check more deeply that the information is coherent.
detail:
func
enhance
asking:
contributor:
|
|
Components release notes
Added an optional 'Components' top-child element, in order to be able to access the components (present via the dependencies, composition and requirements features) that already have an XRN XML release notes defined.
This enable release notes cross references.
This makes the framework more worth, and this becomes interesting.
XMLReleaseNotes2HTML.xsl: the XML to HTML renderer takes benefit of this feature by providing additional hyperlinks on the components references.
Now, an additional feature would be to inline those additional release notes into the generated HTML.
detail:
func
enhance
asking:
contributor:
|
|
XSLT piping
The way the XSL transformations are applied is now more open: additional pre and post treatement is now easier.
detail:
tech
enhance
asking:
contributor:
|
|
|
Dependencies
|
| new |
library
|
See the requirement section. |
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| new |
library
|
This implementation of SAX is necessary for the XML validation agains its schema. It should be present in the Ant 'lib' directory (via the usual 'xercesImpl.jar' Java archive). |
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotes-0.8.0.zip
|
Added the 'XMLReleaseNotes/CumulativeModel.xsl' and 'XMLReleaseNotes/CumulativeLayout.xsl' files, for the cumulative new feature. |
|
|
build date:
2004.05.16
delivery date:
2004.05.16
It is now possible to output several HTML pages for a component.
HTML rendering
It is now possible to output the release notes in multiple HTML pages, one per version.
The status is still very beta, but it can already be used.
detail:
func
enhance
asking:
contributor:
|
|
Open source
The project is now proposed as open-source, so that people can contribute.
detail:
tech
business
asking:
contributor:
|
|
Last version
When the 'lastVersion' parameter did not match to anything in the release notes, no HTML was output: this is now fixed.
detail:
tech
bug-fixing
fix
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotes-0.7.0.zip
|
Additional stylesheets have been added: 'XMLReleaseNotes2HTMLMultiple1.0.xsl' (compliant with XSLT V1.0), 'XMLReleaseNotes2HTMLMultiple2.0.xsl' (compliant with XSLT V2.0) and 'XMLReleaseNotes2HTMLMultipleXalan.xsl' (compliant with Xalan XSLT implementation). |
|
|
build date:
2004.05.09
delivery date:
2004.05.09
This is a minor release that mainly concerns HTML rendering.
Printer friendly
The printer-friendly 'XMLReleaseNotesPrint.css' stylesheet has been significantly improved.
The default CSS has also been changed, in order to easier the customization.
detail:
tech
enhance
asking:
contributor:
|
|
HTML feature detail rendering
Changed the way the feature details (type, why, bug-fixing, category) are layout, so that it is easier to make a printer-friendly CSS.
The 'category' attribute is now being diplayed.
detail:
tech
enhance
asking:
contributor:
|
|
VSC XSLT-model
Fixed this plugin XSLT that was bugged due to the renaming of the 'BuildingBlock' element as 'Item'.
detail:
tech
bug-fixing
fix
asking:
contributor:
|
|
Category
A 'category' attribute has been added the 'Feature' XML element, so as to provide a free additional indicator, that can be handled later on by the XSLT.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.05.06
delivery date:
2004.05.06
An Ant V1.6+ related bug has been fixed.
XMLCatalog bug with Ant V1.6+
The Ant API has changed between Ant V1.5.0 and Ant V1.6: there was a runtime bug because of that. This is now fixed via introspection.
detail:
tech
fix
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.05.04
delivery date:
2004.05.04
Noticeable evolution concerning the HTML rendering. Some structural minor change. Work has begun as far as friendly-printing is concerned.
Printer friendly
CSS: work begun on a CSS that makes the printing friendly via the 'XMLReleaseNotesPrint.css' stylesheet.
The structure has changed a lot.
Still under beat and this probably massively the default CSS structure.
detail:
tech
enhance
asking:
contributor:
|
|
Composition, dependencies and requirements
XSL and Ant: added the 'composition', 'dependency' and 'requirement' parameters that enables to control whether those kind of information should be output or not.
detail:
func
enhance
asking:
contributor:
|
|
HTML rendering
The version and delivery column have disappeared and have been integrated to each release, respectively at the top and at the bottom.
detail:
tech
enhance
asking:
contributor:
|
|
Visibility and Importance
Ant and XSLT: fixed the bug due to the fact that the 'visibility' feature has been changed.
Ant: the 'visibilityThreshold' parameter has been replaced by the 'importanceThreshold' parameter.
detail:
func
fix
asking:
contributor:
|
|
BuildingBlock and Item
XSD: turned the 'BuildingBlock' XML element into 'Item' because this is simpler and more apropriate.
A migration XSLT has been provided in order to migrate existing XRN XML release notes.
detail:
func
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotes-0.6.4.zip
|
An additional CSS has been added, the one which is supposed to become printer-friendly, 'src/XMLReleaseNotesPrint.css'. A new XSLT migration 'migration/XMLReleaseNotesConvertorV0.6.2-0.6.4.xsl' has been added. |
|
|
build date:
2004.05.01
delivery date:
2004.05.01
The previous release notes delivery was wrong because it pointed to V0.6.1.
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.05.01
delivery date:
2004.05.01
XRN has improved as far as migration is concerned. The concept of visibility has been replaced by the concept of importance.
Visibility and Importance
The concept of importance was definitively badly expressed though the 'visibility' concept: this has been replaced by the 'importance' concept.
XSD: the attribute 'visibility' has been replaced by 'importance'.
Use the new migration feature in order to upgrade your XRN XML release notes files.
detail:
func
business
asking:
contributor:
|
|
XRN migration
Ant: added the 'migrate' parameter that enables to automatically migrate the version of the XML release notes file up to the version of the XRN wrapped in the Ant jar.
Since the XSLT are also present in the zip, you can perform the migration via pure XSLT.
detail:
tech
enhance
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.21
delivery date:
2004.04.21
This release fixes bad previous designs, and proposes a first plugin for the integration of CVS change logs into the release notes.
Ant task mail re-engineering
It was definitively a bad idea to inline the mail task at the same XML hierarchy level as the XRN task's. The mail task is now an inner XML element, and the 'mail' parameter is discarded.
You can now provide a specific subject to the sent-mail via the 'subject' parameter of the inner 'mail' XML element.
detail:
tech
bug-fixing
enhance
asking:
contributor:
|
|
Versioning Control System
Enables a deeper integration with the VCS systems, so that it is possible to track down the source changes.
This enables to produce more accurate and exhaustive release notes, dedicated to the support of the component.
This opens the framework to the versioning system and enhance this information, that is too often restricted to developers, when they take the time to make views...
This is now possible for CVS via the 'plugin/CVSModel.xsl' XSLT model file: beta for the moment, because it lacks integration...
detail:
func
asking:
contributor:
|
|
Feature new type
Added the 'vsc' feature type so as to render this feature a different way via the XSLT: not yet taken into account.
detail:
func
enhance
asking:
contributor:
|
|
The 'why' feature attribute
Added the 'why' attribute to the 'Feature' XML element, in order to better understand the reason for the feature. This enables to better understand the evolution of the component.
This enables to open the framework to existing solutions that deal with the needs collecting.
This attribute is not yet taken into account...
detail:
func
business
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.20
delivery date:
2004.04.20
This version adds the Ant 'mailing' feature, proposes to inline the CSS, so as to make possible stand-alone HTML release notes pages.
Feature visibility
XSL: added CSS selector classes named 'featureVisibilityN' in order to give control to a feature visibility, where N ranges from 1 to 4.
detail:
tech
asking:
contributor:
|
CSS inlined
Ant: it is now possible to inline the CSS content within the generated HTML, so as to be make some HTML stand-alone. This is possible via the 'inlineCSS' parameter.
detail:
tech
asking:
contributor:
|
|
New dependency, composition, requirement
XMLReleaseNotes2HTML.xsl: fixed the problem of the '[from M.m.µ]' display when [new] also appears (dependencies, requirements, composition).
detail:
tech
bug-fixing
asking:
contributor:
|
|
Improvement of the Feature ID
A better HTML rendering of the feature inheritance and its identifier is now performed.
detail:
tech
asking:
contributor:
|
|
Mail
Ant: added the opportunity to mail the release notes directly from the task, since the task derives from the official Ant 'Mail' task.
detail:
tech
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.5.1
|
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.15
delivery date:
2004.04.15
Some XSLT technical improvements and some functional additions is the HTML rendering.
Reuse of the Feature ID
Pay more attention to the 'ID' of a 'Feature' element and refer to it if already defined in the past. Now hyperlinks are displayed for already defined features.
detail:
tech
asking:
contributor:
|
|
HTML content
Enable a better way to express that some HTML tags may be used within the XML release notes, as far as textual content is concerned: the 'contentType' attribute has been added to nearly all textual possible places. When set to 'html', you can use HTML tags. This is now possible but do not abuse it because you have to think that those release notes may be output in other formats than HTML!...
detail:
tech
asking:
contributor:
|
|
URI resolver and parameters
Ant: added the opportunity to use URI resolvers in the XSLT provided by the user via the inner 'xmlcatalog' XML element within the 'model' and 'layout' elements. This is the native Ant XMLCatalog element.
Ant: added the possibility to provide XSLT parameters in the task via the inner 'param' element within the 'model' and 'layout' elements. This is a copy of the built-in 'XSLT' task Ant feature.
detail:
tech
asking:
contributor:
|
|
Feature 'ID' attribute
Made this 'Feature/@ID' attribute a string, so that mnemonics may be used.
detail:
func
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| Beware of the Ant requirement that has changed. |
| new |
software
|
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.14
delivery date:
2004.04.14
Opened the framework so that it is possible some external information from the outer via the Ant task.
Additional XSLT
Ant: added the possibility to use additional XSLT in order to open the framework via the 'model' and 'layout' inner elements.
detail:
func
asking:
contributor:
|
|
Abstract
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
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.3.2
|
software
|
Only if you want to use with Ant: the task has been tested from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.13
delivery date:
2004.04.13
Better package of the delivery, introduction of the concept of version of the framework.
Added a version attribute that enables to track the version of the framework used. This may be very useful as far as migration and converstions are concerned.
XSD: added the 'version' attribute indicates the version of the XMLReleaseNotes framework it complies to.
XSL: outputs this version in the bottom banner and outputs a warning if the XML release notes and the XSD are not the same version.
detail:
tech
asking:
contributor:
|
|
Fixed the bug of the delivery download hyperlink that was wrong.
detail:
tech
bug-fixing
asking:
contributor:
|
|
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
asking:
contributor:
|
|
Fixed the release which missed the release notes! How possible is it?
detail:
tech
fix
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.3.2
|
software
|
Only if you want to use with Ant: the task has been tested from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotes-0.4.1.zip
|
Fixed the content of the delivery. The naming convention of the delivery file name has changed and is now 'XMLReleaseNotes-M.m.p.zip'. The sources ar now placed within the 'src' directory. A readme file has been added. |
|
|
build date:
2004.04.12
delivery date:
2004.04.12
This is a technical release that makes the framework more integrable.
Ant: added the 'deploy' parameter that enables to deploy the framework resources from the jar library, so as to be able to use the XSD, the CSS...
detail:
tech
asking:
contributor:
|
|
Ant: removed the default 'stylsheet.css' file into a directory named 'XMLReleaseNotes' into the jar library, so as to possible avoid conflicts with the rest of the classpath.
detail:
tech
asking:
contributor:
|
|
XSL: turned the 'standAloneHTML' parameter default value to 'false'.
detail:
tech
asking:
contributor:
|
|
Fixed the bug concerning the 'Requirements', 'Dependencies' and 'Composition' display, which were not always present as required.
detail:
tech
bug-fixing
asking:
contributor:
|
|
Made the 'Release/@deliveryDate' optional, because you can build releases without never spreading them!
detail:
func
asking:
contributor:
|
|
XSD: the schema now belongs to the 'http://xmlreleasenotes.free.fr' target namespace, which should be refered as 'xrn'.
detail:
tech
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.3.2
|
software
|
Only if you want to use with Ant: the task has been tested from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.07
delivery date:
2004.04.07
The website is more elaborated. Just changed a few key things within the XSD.
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
asking:
contributor:
|
|
Added the opportunity to define a release builder via the 'builderID' attribute on the 'Release' element.
detail:
func
asking:
contributor:
|
|
XMLReleaseNotes2HTML.xsl: added the 'delivery' parameter that enables not to output de "Delivery" column, which enables to download the artefacts.
detail:
func
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| from
0.3.2
|
software
|
Only if you want to use with Ant: the task has been tested from this version of Ant. |
| from
0.3.2
|
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
|
build date:
2004.04.01
delivery date:
2004.04.01
The idea is to provide a first basic Ant integration.
Added an Ant-task Java library that enables XMLReleaseNotes HTML transformation seamless integration to Ant.
detail:
tech
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| The requirements have changed concerning the Ant integration, which is a new feature. |
| new |
software
|
Only if you want to use with Ant: the task has been tested from this version of Ant. |
| new |
|
You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. Both are tested and should work with XRN. |
|
Deliveries
|
|
XMLReleaseNotesV0.3.2.zip
|
An additional Ant Java task library is available under 'lib' and a new directory 'doc' has been created. |
|
|
build date:
2004.03.31
delivery date:
2004.03.31
This is a very tiny incrementation compared to the previous release.
Added an an about page on the web-site.
detail:
func
asking:
contributor:
|
|
The releases sorting is better thought. The need of a documentation is now needed.
detail:
func
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.30
delivery date:
2004.03.30
This is a version that can already be used as far as HTML transformation is concerned..
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.
detail:
func
asking:
contributor:
|
|
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
asking:
contributor:
|
|
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
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.26
delivery date:
2004.03.26
This is a version that presents a better HTML transformation.
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.21
delivery date:
2004.03.21
Added the opportunity to use a CSS when transforming into HTML via the 'XMLReleaseNotes2HTML.xsl'.
XMLReleaseNotes2HTML.xsl: you can now define the lower and upper limits of the versions for which the HTML is generated.
detail:
func
asking:
contributor:
|
|
|
Dependencies
|
| from
0.2.4
|
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| from
0.2.4
|
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Deliveries
|
|
XMLReleaseNotesV0.2.5.zip
|
The delivery now contains the licenses and a default CSS stylesheet named 'stylesheet.css'. |
|
|
build date:
2004.03.21
delivery date:
2004.03.21
There is no new delivery, only the web site generation has changed and contains the internal AntDoc.
|
Dependencies
|
| new |
software
|
WedSitor is required on the development side, because this is the component responsible for generating the web site. You should have the 'WedSitor.jar' present in you Ant 'lib' directory. |
| new |
software
|
AntDoc is required when developing because it is being used when generating the web site. You should have the 'AntDoc.jar' present in you Ant 'lib' directory. |
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.21
delivery date:
2004.03.21
This is patch and the top-child 'Deliveries' XML element has been added so as to express the delivery root URL.
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
asking:
contributor:
|
|
|
Dependencies
|
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.21
delivery date:
2004.03.21
This is the very first downloable release.
|
Dependencies
|
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
Requirements
|
| This is just how to show that you may not inherit from the previous requirements. |
|
Deliveries
|
| The V0.2.0 and V0.2.1 were not OK, as far as the automatic delivery process is concerned. |
|
XMLReleaseNotesV0.2.2.zip
|
The delivery is a simple zip, not yet totally properly organized. |
|
|
build date:
2004.03.21
delivery date:
never
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.
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
asking:
contributor:
|
|
|
Dependencies
|
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
build date:
2004.03.18
delivery date:
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.
|
Dependencies
|
| from
0.0.alpha
|
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| from
0.0.alpha
|
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| from
0.0.alpha
|
standard
|
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
|
software
|
This component is required in order to ensure the build process managment. |
|
|
XMLReleaseNotes 0.0.alpha
|
|
|
build date:
2004.03.18
delivery date:
never
This version is a first try to build a tiny XML release notes framework.
|
Dependencies
|
| new |
standard
|
XSD is being use so as to restrict and standardize the release notes structure. |
| new |
standard
|
All the tiny framework is expressed in XML, so this is of course required to build it. |
| new |
standard
|
The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| new |
software
|
This component is required in order to ensure the build process managment. |
|
Deliveries
|
| No delivery available at this stage. This framework has been initialized in 2002, I have already used it, but this is the first time that it is packaged. |
|