API Version numbers should not be replaceable about apibuilder

[mbryzek]

I think you're right - but I'm a bit torn on this given how useful this is in development. Maybe we introduce a single "-SNAPSHOT" flag to indicate those are changed? Aligns to how we've done this elsewhere at gilt

[brazir]

The snapshot approach seems fine where the iterations are all generated as snapshot and then a single publish occurs for a version number.

[xetorthio]

We should follow semver probably. It is widely used in yhe opensource
community.
I am not sure how semver addresses this specific issue though. I will check.
On May 1, 2014 9:29 AM, "Rob" [email protected] wrote:

The snapshot approach seems fine where the iterations are all generated as
snapshot and then a single publish occurs for a version number.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-41909647
.

[mbryzek]

Internally, version is a string. This allows anybody to upload whatever version number they want.

If a version number starts with a "number" followed by "dot" repeated as many times - we can identify that version string and do proper sorting. So users who use semver versioning will get natural, proper ordering.

Users that use different ordering will get maybe wrong ordering but will still work. You can see the tests related to version numbers at:

api/test/lib/VersionSortKeySpec.scala

I think the open question here is at what point do we support locking the interface and no longer accepting changes to the published API. I'm not 100% sure yet what the best workflow for this is so let's leave this issue open for now