Profile version naming

• I use self-explaining names for end user profiles.

• End user profiles differ from the mother hiking/(bike)treking template just by tweaking some logical a/o numerical parameters place in the header.

• There is a history log at the bottom of each profile, describing development history of the template, with internal bersion numbering.

• Internal version numbering is in form M.N.X STATUS

  • M is major version, means major profile rewrites
  • N is minor version, means usually different GITHUB development branches with (major) different a/o alternative features.
  • X is development version, addressing fixes, minor new or modified feature modifications.
  • STATUS is
    • ALFA - Experimental a/o under development profile template version. It may improve the thinks as well as ruin them. Expect all kind of surprises like routing to a pit full of hungry wolves.
    • BETA - Profile template version with new featured quite settled, usually after limited testing on Brouter web. There is high probability of future change of new features. Experimenting users are encouraged to try them, but be prepared they may need some tuning. Feedback is welcome, especially if you know working with github better then me.
    • RELEASE - Profile template tested in Brouter-web, and with (limited) testing outdoors, with quite satisfying results. Tuning feedback is still welcome. Ready to be used for deriving the final end user profiles variants.

• I frequently backport the code to older development branches of the templates, if the code can be applied to the common code of the branches.