Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 3railML 3
  • Issues
  • #458
Closed
Open
Issue created Feb 15, 2021 by Coordination@coordination.GOVOwner

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:

  1. Connect by [[https://en.wikipedia.org/wiki/SSH_(Secure_Shell)|SSH]] with [[ssh://dev.railml.org|dev.railml.org]] as root user
  2. cd /srv/svn/
  3. Choose correct path {railML2|railML3}, tag name as well as description
  4. 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"
  5. Notice SVN number after this action (here: 1091)
  6. svnadmin setrevprop /srv/svn/railML -r 1091 svn:author <(echo -n vasco.kolmorgen)
  7. cd ../trac/
  8. ./railMLresync.sh
Edited Apr 14, 2022 by Organisation
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany