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.

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

Versioning in BCT #1925

Closed
ghost opened this issue Dec 3, 2020 · 3 comments
Closed

Versioning in BCT #1925

ghost opened this issue Dec 3, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Dec 3, 2020

There Is something strange in versioning in BCT.
I like how Node does.
<= Is not equal to not supported or deprecated so red?

https://docs.npmjs.com/about-semantic-versioning

Screenshot_20201203-195105.png

@peterbe
Copy link
Contributor

peterbe commented Dec 4, 2020

There's a duplicate of this already. Do you think you can search and find it?
I guess what you're saying is that ≤37 means that it's not supported in version 38 and onwards, therefore it should be red. Is that what you mean?
Also, what does that have to do with semantic versioning? What's the connection?

@ghost
Copy link
Author

ghost commented Dec 4, 2020

#1607

Yes I mean that, if version now is 2, less than 2 is red.
Semantic versioning seem talks only about going Up and not Down so the past does not care but only the future does.
At least block to something in time until some Bot do not PR for You.

Semantic versioning seems to be a good synopsis.

@peterbe
Copy link
Contributor

peterbe commented Dec 4, 2020

Thanks for finding the dupe.

@peterbe peterbe closed this as completed Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant