id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3328	Future version numbers	Martin Sjölund	somebody	"I propose we change the OpenModelica versions to follow http://semver.org/ more closely.

Currently, the next release is proposed to be 1.9.3, which would correspond to a patch level release. It really should be 1.10.0 (or 2.0.0 since we probably introduced some backwards-incompatible changes).

This would also make it possible to create branches for maintenance releases and still have sane version numbers for them.

So you have a:
release 2.0.0, followed by a tag 2.1.0-dev. So nightly builds are called 2.1.0-dev.1, 2.1.0-dev.2, etc.
On the branch, the parent commit is 2.0.0, which is followed by tag 2.0.1-dev (or possibly just saying that the commits after are released as 2.0.1, 2.0.2, etc).

We could also skip tagging 2.1.0-dev and 2.0.1-dev, but then the name depends on which branch the commit is part of, which is harder to determine."	discussion	closed	high		Build Environment	trunk	fixed		openmodelicadevelopers@…