Ctags: Decide on versioning scheme

Created on 6 Nov 2015 · 8Comments · Source: universal-ctags/ctags

@masatake brought this up here: https://github.com/universal-ctags/ctags/issues/652#issuecomment-153411749

I prefer using semver and starting with 1.0.0 since Universal Ctags != Exuberant Ctags. @masatake prefers 6.0.

When this discussion is resolved:

[ ] Update the name of the "Initial release" milestone to whatever is decided here as the first "stable" release version

I'm also in favor of having an earlier non-stable release (just for the sake of putting a line in the sand that people working on packaging can reference), perhaps 0.1.0?

cc @universal-ctags/admins @universal-ctags/developers

General discussioQuestions

Source

cweagans

Most helpful comment

I propose we do the following:

Rename the initial release milestone to "1.0.0"
When all the issues in the 1.0.0 milestone are closed, we tag 1.0.0-rc1
After a month, if there are no more critical, release-blocking issues, we tag 1.0.0. If there are, we fix them, and tag 1.0.0-rc2, rinse, and repeat until we can get through an entire month without release blocking issues.

@universal-ctags/admins any objections to this ^?

cweagans on 12 Nov 2015

👍2

All 8 comments

@cweagans, I follow your proposal: 1.0.0 and 0.1.0.

masatake on 9 Nov 2015

I propose we do the following:

Rename the initial release milestone to "1.0.0"
When all the issues in the 1.0.0 milestone are closed, we tag 1.0.0-rc1
After a month, if there are no more critical, release-blocking issues, we tag 1.0.0. If there are, we fix them, and tag 1.0.0-rc2, rinse, and repeat until we can get through an entire month without release blocking issues.

@universal-ctags/admins any objections to this ^?

cweagans on 12 Nov 2015

👍2

Sounds good to me.

Just think that 0.1.0 is a bit low. 0.9.0 sounds more like we are working towards a proper release.