-
Notifications
You must be signed in to change notification settings - Fork 887
Release timeline for TSLint v6 #4811
Comments
Sounds good to me 👍 |
Bump @adidahiya - are you able to publish a minor version update? |
@JoshuaKGoldberg sorry for the delay, I was OOTO the past 2 weeks... I can release a minor version this week. |
@adidahiya Thanks this would be great, am aching to get at a rule I contributed |
5.19.0 is released now |
updated release timeline in OP |
😅 looks like we blew past that timeline. The 'breaking change' issues and PRs now ok to merge are linked here. I'll edit the revised timeline in the OP to push forward a month and start merging these in (read: bugging authors for merge conflicts). FYI @adidahiya |
@adidahiya I think we're ready to release a beta? |
@JoshuaKGoldberg sounds good, it's on my list to do this weekend. |
just released v6.0.0-beta0 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@adidahiya are we ready to release |
6.0.0 has been released and marked as deprecated on NPM. This will mean that new installs of the package will get the warning, while existing installs of 5.x will not.
|
There are a bunch of otherwise-actionable issues and pull requests marked as breaking changes. Let's come up with a timeline for getting to that fabled TSLint 6.x version! 🙌
Straw man proposal:
removeignore 'breaking change' label from existing issues & PRs, and start merging them intslint@6.0.0-beta0
tslint@6.0.0-beta1
tslint@6.0.0
Thoughts?
/cc @adidahiya
Updated proposal
9/39/910/4:tslint@6.0.0-beta0
tslint@6.0.0-beta1
tslint@6.0.0
The text was updated successfully, but these errors were encountered: