Replies: 5 comments 3 replies
|
Following ESLints versioning policy sounds a good idea. 👍 I've searched for @typescript-eslint's versioning, but I couldn't find one. So The two big repos we should look at are having the same policy and so should we imo. |
|
The ESLint versioning policy sounds great. I would've expected any change to |
|
Alright, I'll add the Semantic Versioning Policy next week. My idea is to put it in its own file under |
|
Taking a closer look at how @typescript-eslint is handling this: they don't seem to follow the ESLint versioning policy. Although they sometimes are:
I'll create an issue on their repo in order to ask what versioning policy they're using, so we can take that into account when deciding what way we go. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey there!
I think we need to define a Semantic Versioning Policy so:
I think Semantic Versioning Policy from ESLint itself is the best option and we should stick to that. The idea then would be to mirror it in our README and CONTRIBUTING docs, just changing
eslint:recommendedby our available Shareable Configs.What do you think? @gndelia @timdeschryver @MichaelDeBoey
All reactions