Skip to content
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.

How should EthOn be versioned? #3

Closed
jo-tud opened this issue Dec 19, 2016 · 3 comments
Closed

How should EthOn be versioned? #3

jo-tud opened this issue Dec 19, 2016 · 3 comments
Labels

Comments

@jo-tud
Copy link
Contributor

jo-tud commented Dec 19, 2016

My suggestion is to go public with 0.1.0 and set the owl:versionIRI to http://ethon.consensys.net/1/.

  • From then on act according to http://semver.org/ (MAJOR.MINOR.PATCH)
  • Then, only when we come to 1.0.0 the version IRI increases.
  • Releases should be done via GitHub tagging.
  • Development will take place in dev branch.
  • The latest version will always be http://ethon.consensys.net.

(thanks @kumavis for this suggestion)

@axic
Copy link

axic commented Dec 20, 2016

@jo-tud keep in mind one little aspect of semver: the difference between major 0 and major 1.

With major 0, the work is in beta phase and any breaking change will result in a minor bump. With major 1, the work is over the beta phase and any breaking change will result in a major bump.

In short, you could inflate the major very quickly if breaking changes are expected.

@jo-tud
Copy link
Contributor Author

jo-tud commented Dec 21, 2016

@axic
Yes, that's right. We will start with version IRI ethon.consensys.net/0/ and version 0.1.0
(updated above)

@jo-tud
Copy link
Contributor Author

jo-tud commented Jan 20, 2017

@jo-tud jo-tud closed this as completed Jan 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants