Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clear rules on version stepping are needed #189

Closed
d-stahl-ericsson opened this issue Apr 18, 2018 · 0 comments
Closed

Clear rules on version stepping are needed #189

d-stahl-ericsson opened this issue Apr 18, 2018 · 0 comments

Comments

@d-stahl-ericsson
Copy link
Contributor

Description

Currently there are no clear rules on when to step major, minor and patch versions when event types are updated. This leads to a judgment call every time, as determining version impact of a change is not as straight-forward as with an API.

Motivation

Consistency and clarity when making changes to event types.

Exemplification

PR #188

Benefits

Every time change to event type syntax or semantics is proposed, we wouldn't have to have a conversation about whether the new version should be e.g. 1.0.1, 1.1.0 or 2.0.0.

Possible Drawbacks

Can't really think of any.
d-stahl-ericsson added a commit to d-stahl-ericsson/eiffel that referenced this issue Aug 7, 2018
@d-stahl-ericsson
Add rules for patch, minor and major version increments
22ce5eb 
As per issue eiffel-community#189, added version stepping rules in versioning.md.
@d-stahl-ericsson d-stahl-ericsson mentioned this issue Aug 7, 2018
Merged
d-stahl-ericsson added a commit that referenced this issue Aug 28, 2018
@d-stahl-ericsson
Add rules for patch, minor and major version increments (#196)
ca97a3f 
Addressing issues #189 and #200, added detailed rules and guidelines for when and how to step event type versions, and how to update historical event type versions and/or editions.
@d-stahl-ericsson d-stahl-ericsson mentioned this issue Aug 28, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d-stahl-ericsson