docs: Add 2026-02-05 meeting notes (#674)

* docs: Add 2026-02-05 meeting notes

* add transcript

---------

Co-authored-by: Milos Djermanovic <milos.djermanovic@gmail.com>

Author: sam3k

notes/2026/2026-02-05.md

@@ -0,0 +1,97 @@
+# 2026-02-05 ESLint TSC Meeting Notes
+
+## Transcript
+
+[`2026-02-05-transcript.md`](2026-02-05-transcript.md)
+
+## Attending
+
+- Nicholas C. Zakas (@nzakas) - TSC
+- Milos Djermanovic (@mdjermanovic) - TSC
+- Francesco Trotta (@fasttime) - TSC
+
+@nzakas moderated, and @sam3k took notes.
+
+## Topics
+
+### Follow-up from Previous Meeting
+
+**TSC Summary:** No action items from the previous meeting.
+
+### Statuses
+
+* **@nzakas:** Unexpectedly didn't have much time over the past two weeks, so mostly focused on issue/PR triage.
+* **@mdjermanovic:** Was working on tasks for the final ESLint v10.0.0 release and reviewing PRs.
+* **@fasttime:** Worked on removing `FlatESLint` and `LegacyESLint` exports and adding support for `Array.fromAsync` to core rules, and reviewing PRs.
+
+### Availability Next Two Weeks
+
+* **@nzakas:** Should mostly be back to 0.5-1 hours per weekday for the next two weeks.
+* **@mdjermanovic:** Should be available around 1-1.5h each day.
+* **@fasttime:** Expects to be available 7-9 hours per week the next two weeks.
+
+### RFC Duty Update
+
+* This week: @nzakas
+* February 9: @mdjermanovic
+* February 16: @fasttime
+
+### V10.0.0 Release Planning
+
+**TSC Summary:** The team reviewed the readiness for the final v10.0.0 release scheduled for February 6th.
+
+**Discussion Points:**
+- All PRs are prepared and have at least one approval
+- Release tasks are documented in two issues:
+  - [Issue #20326](https://github.com/eslint/eslint/issues/20326) - Revert temporary changes (not urgent, can be done after release)
+  - [Issue #20459](https://github.com/eslint/eslint/issues/20459) - Prepare final v10.0.0 release (important for the release)
+- Some PRs can be merged in advance to reduce work during release time
+- @mdjermanovic tested the release process locally and everything seemed fine
+- @mdjermanovic will not be available on February 6th
+
+**PRs to Merge in Advance:**
+- [PR #20452](https://github.com/eslint/eslint/pull/20452) - Link checker PR (safe to merge now)
+- [PR #20453](https://github.com/eslint/eslint/pull/20453) - Link checker PR (safe to merge now)
+- [PR #20466](https://github.com/eslint/eslint/pull/20466) - Likely safe to merge now (CI passing)
+- [PR #20467](https://github.com/eslint/eslint/pull/20467) - Likely safe to merge now (CI passing)
+
+**PRs to Wait Until Release Time:**
+- 3 remaining PRs should wait (1 right before release, 2 right after)
+
+**Release Details:**
+- For `eslint` release: `RELEASE_TYPE` should be `latest`, `RELEASE_BRANCH` is `main`
+- For `@eslint/js` release: `RELEASE_TYPE` should be `patch` (releasing 10.0.1 to skip already published 10.0.0), `RELEASE_BRANCH` is `main`
+
+**Resolution:** The TSC confirmed readiness for the v10.0.0 release on February 6th.
+
+**Action Items:**
+- @nzakas will:
+  - Do the release on February 6th about an hour after meeting time
+  - File an issue with EasyCLA to add ESLint Bot commits as an exception ([Infrastructure Issue #100](https://github.com/openjs-foundation/infrastructure/issues/100))
+
+- @fasttime will:
+  - Be available during the release for a second set of eyes
+
+### [Contributor Pool for January](https://github.com/eslint/tsc-meetings/blob/main/notes/2026/2026-02-01-contributor-pool.md)
+
+The TSC reviewed contributions from the January contributor pool report.
+
+**Budget:** $916 available
+
+**Discussion Points:**
+- Some PRs were quite small compared to others
+- Sethamus and ntnyq's PRs were particularly small
+- patricktree and ST-DDT had the largest PRs
+- xbinaryx also had a significant contribution
+- cryptnix was also fairly small
+- The team doesn't have to award all available budget
+
+**Final Distribution:**
+- patricktree: $400
+- ST-DDT: $300
+- xbinaryx: $200
+
+**Total:** $900
+
+**Action Items:**
+- @nzakas will notify the recipients