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

Add guidelines for deprecating tools. Deprecate jshint and jslint #224

Merged
merged 1 commit into from
Jan 31, 2019

Conversation

mre
Copy link
Member

@mre mre commented Jan 30, 2019

This fixes #223.
As discussed in the thread, I'm also adding guidelines on how to mark tools as deprecated/unmaintained to the documentation.

Copy link
Collaborator

@impredicative impredicative left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. To be clear, there are certain criteria for which a tool would need to get unlisted, and the warning symbol wouldn't apply to those.

@mre
Copy link
Member Author

mre commented Jan 30, 2019

To be clear, there are certain criteria for which a tool would need to get unlisted, and the warning symbol wouldn't apply to those.

Fully agree. For example, if critical security vulnerabilities don't get fixed in a timely manner. Maybe we should add a section about fully unlisting tools, but that's a bit out of the scope of this PR. Important point however.

@mre mre merged commit 9c26429 into master Jan 31, 2019
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

Successfully merging this pull request may close these issues.

JSHint and JSLint are outdated
2 participants