Recurring tasks BEFORE creating a version (de: Wiederkehrende Aufgaben VOR dem Anlegen einer Version)
This ticket is to describe all recurring administrative tasks before creating (tagging) a new version. It is irrelevant whether this is an alpha, beta, RC or final version. This is an ongoing and neverending task ... (Therefore, after finishing a version, please assign this ticket to the next version to be released).
-
Schema
- Manual [[https://en.wikipedia.org/wiki/Geography_Markup_Language|GML]] correction
-
Documentation
- Create inline documentation with [[https://www.altova.com/xmlspy-xml-editor|XMYSpy]]
- Add new, changed or removed elements and attribute in the changelog in [[https://wiki2.railml.org/wiki/Dev:Changes|Wiki2]] or [[https://wiki3.railml.org/wiki/Dev:Changes|Wiki3]]
-
Repository files
- Remove or update outdated example files
- Remove all unnesseary files like _railML-...changelog.txt
A final tag shall consist of the following folders only:
- codelists/
- documentation/
- model/ _(railML 3 only)_
- schema/
To tag a new version please follow these steps:
- Connect by [[https://en.wikipedia.org/wiki/SSH_(Secure_Shell)|SSH]] with [[ssh://dev.railml.org|dev.railml.org]] as root user
cd /srv/svn/
- Choose correct path {railML2|railML3}, tag name as well as description
svn copy file:///srv/svn/railML/railML3/trunk file:///srv/svn/railML/railML3/tags/railML-3.2-alpha1 -m "Alpha1 for railML version 3.2"
- Notice SVN number after this action (here: 1091)
svnadmin setrevprop /srv/svn/railML -r 1091 svn:author <(echo -n vasco.kolmorgen)
cd ../trac/
./railMLresync.sh