This page focus on how to get started with XRN.
Enough talked about the philosophy and so on. Now we need to evaluate the solution, to see it working For that, there are prerequisites like any system.
An important matter: we are trying to define a release notes for a precise version of a component. What do we call "component"? A program, a library, a project, some activity that yields delivery artifacts (the framework could have been named "Artifact", indeed).
This component is about to be released because some new needs have been expressed, designed and developed for that new release, the name of the release, the version, has been identified and name. Bugs have been solved by the same way.
What would be great now, is to present and remember those changes, the release notes. Of course, you can write a plain text file, version and save it, but this is kind of a poor solution. If you have a tool that enables to enhance this information without wasting time to use it, you'll get happy.
If you want to spare some time, we advise you to read on the rest of this section, by visiting each tab from left to right. We are going to see how to use the XRN framework.
The current documentation is present in the XRN zip devliery package file, under