-
Notifications
You must be signed in to change notification settings - Fork 13
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
TSC meeting 13-August-2020 #198
Comments
It would be nice to define semver policy for bug fixes in rule schemas, specifically for those fixes that can cause schema validation errors in existing configs (if the rule was misconfigured in user's config, but the schema was incorrect/incomplete and didn't catch that). Additionally, and if the decision is to treat these as semver-major changes, should we revert eslint/eslint#13166. |
To be clear - anything that causes correct linting warnings in code to appear imo is not semver-major, however, anything that causes a schema failure crashes the entire eslint run. My preferred outcome would be that "string, override object" became valid for |
@mdjermanovic can you clarify if your intent here is to add an agenda item to the meeting? |
Yes, I thought it would be good to discuss this since it's about semver policy (if it isn't already covered by the policy). |
Yup, that's fine. In the future, if you can just prefix with "Agenda item:" or "I'd like to discuss", it will make things a bit clearer. Thanks! |
Agenda item: Let's discuss what types of companies and organizations we want to accept donations from. For example, we probably don't want to accept donations from any of the following:
It would be good to get this documented, as it might help us avoid needing to refund and block groups on Open Collective. |
Time
UTC Thu 13-Aug-2020 20:00:
Location
https://eslint.org/chat/tsc-meetings
Agenda
Extracted from:
Invited
Public participation
Anyone is welcome to attend the meeting as observers. We ask that you refrain from interrupting the meeting once it begins and only participate if invited to do so.
The text was updated successfully, but these errors were encountered: