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

[INCONSISTENCY] Escalate semantic versioning #8

Closed
orviz opened this issue Feb 7, 2019 · 3 comments
Closed

[INCONSISTENCY] Escalate semantic versioning #8

orviz opened this issue Feb 7, 2019 · 3 comments
Assignees
@orviz
Labels
inconsistency This doesn't seem right

Comments

@orviz
Copy link
Member

orviz commented Feb 7, 2019 •
edited
Loading

Describe and locate the inconsistency
Usage of semantic versioning is currently RECOMMENDED.

Expected content
Escalate it to MUST verb.
@orviz orviz added the inconsistency This doesn't seem right label Feb 7, 2019
@orviz orviz self-assigned this Feb 7, 2019
@mariojmdavid
Copy link
Contributor

I agree

@caifti
Copy link

caifti commented Mar 14, 2019

When we'll have time I would like to have a more deep discusion on this.
Anyhow I agree on making more relaxed, and reffer also to some specific standards.

@orviz
Copy link
Member Author

orviz commented Mar 27, 2019

Hi @mariojmdavid @caifti

indeed there is a typo in the expected content, it says SHOULD while I meant MUST (SHOULD == RECOMMENDED). From the comments above, and with the perspective of time :P, we can probably leave it as a recommendation, since MUST appears way too restrictive.

I will close this issue and leave the discussion for the Release conventions issue #17

@orviz orviz closed this as completed Mar 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@orviz orviz

Labels
inconsistency This doesn't seem right
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@caifti @orviz @mariojmdavid