Administrative

Projects

Active

Future

Finished

Reference

Abandoned

My version numbering system

My software version numbers are created using a simple system. Hardware version control is described on another page

There is also a reference to my git workflow.

With [version] being a dot-separated string containing the major and minor version number (e.g. "1.3"), the version strings are created as:

devel-[version]
beta-[version]
release-[version]

XX-YNN.MM

HEAD-YYYY-MM-DD

For example:

devel-1.0
beta-1.3
release-2.5
CL-P01.01
HEAD-2007-07-14

devel versions are normally not released to the public and mark source code currently under development. A devel version is created when some status of usability has been achieved during development. The source code created from devel versions is marked post-devel-[version], but (tech info) a git tag is not created. If a beta or release version is created, the counters in [version] continue not regarding the numbering of the other versions. This makes finding the last stable version a bit complicated, but keeps the threads devel, beta and release separated more strictly.

beta versions are are released to the public for testing purposes and may contain bugs. Please report bugs via email to the address given in the software's documentation.

release marks versions which are considered bug-free and are intended to be used in real life. Though I do my best to eliminate all these bugs in the software before releasing it, I can not give any warranties that the software will fit any special purpose, or will not cause some damage. I shall not be held liable for damage caused by my software, and so on. Include standard disclaimer here.

The XX-YNN.MM git tags are a special case for programs that belong to a larger project that is included in the part number designator list. These tags are actually part numbers described on the respective project page parts overview.

HEAD revisions are snapshots from the git source repository taken on the given date. These are the current state of development, and published in between of either devel releases or before a XX-YNN.MM part number is assigned.

The XX codes are registered in the part number registry.

Logbook