-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: Add 2023-09-07 meeting notes (#454)
- Loading branch information
Showing
1 changed file
with
41 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# 2023-09-07 ESLint TSC Meeting Notes | ||
|
||
## Transcript | ||
|
||
[`2023-09-07-transcript.md`](2023-09-07-transcript.md) | ||
|
||
## Attending | ||
|
||
* Nicholas C. Zakas (@nzakas) - TSC | ||
* Milos Djermanovic (@mdjermanovic) - TSC | ||
|
||
@nzakas moderated, and @sam3k took notes. | ||
|
||
## Topics | ||
|
||
### [New v9.0.0 Candidates](https://github.com/orgs/eslint/projects/4/views/1) | ||
|
||
| Feature | 👍 | 👎 | 🤷♂️ | Notes | | ||
| ------- | -- | -- | - | ----- | | ||
| [Change Request: Deprecate and remove `CodePath#currentSegments`](https://github.com/eslint/eslint/issues/17457) | 2 | | | | | ||
| [Bug: Comment directives with just severity overrides options](https://github.com/eslint/eslint/issues/17381) | 2 | | | | | ||
| [Change Request: Remove all formatters except stylish, json, and json-with-meta](https://github.com/eslint/eslint/issues/17524) | 1 | | 1 | TBD | | ||
| [Change Request: Deprecate formatting rules and recommend using a source code formatter](https://github.com/eslint/eslint/issues/17522) | 2 | | | Pending the list of rules | | ||
|
||
#### Regarding issue [#17524](https://github.com/eslint/eslint/issues/17524) | ||
|
||
**Summary:** There were some concerns regarding breaking some integrations that expect certain formatters. We'll post the issue on Twitter and Mastodon to see if we can get some early feedback on potential issues. | ||
|
||
**Resolution:** We've agreed to include this issue in v9 with a note that we can use the beta period to evaluate the safety of this change and reverse course if necessary. | ||
|
||
### v9 Release Strategy | ||
|
||
**Summary:** Could we simplify our merging strategy by introducing a `v9-candidate` branch to which we merge PRs into? Then, once ready, we can submit a PR from `v9-candidate` to `main`. | ||
|
||
**Resolution:** @mdjermanovic will investigate how Node.js solve this. We have an [example](https://github.com/nodejs/node/pull/49528) of how Node.js does it. | ||
|
||
### Scheduled release for September 8th, 2023 | ||
|
||
**Action Items:** @mdjermanovic will handle the release: | ||
* `eslint` | ||
* `eslint/js` |