Opened 10 years ago

Closed 8 years ago

Last modified 7 years ago

#3328 closed discussion (fixed)

Future version numbers

Reported by: Martin Sjölund Owned by: somebody
Priority: high Milestone:
Component: Build Environment Version: trunk
Keywords: Cc: openmodelicadevelopers@…

Description

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.

Change History (5)

comment:1 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:2 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:3 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:4 by Francesco Casella, 8 years ago

Resolution: fixed
Status: newclosed

This has been implemented since 1.10.0

comment:5 by Martin Sjölund, 7 years ago

Milestone: 1.10.0

Milestone deleted

Note: See TracTickets for help on using tickets.