Skip to content

Comments

Add libraries.md for .NET 11 Preview 2#10267

Open
jamesmontemagno wants to merge 3 commits intodotnet11-preview2from
dotnet11-preview2-libraries
Open

Add libraries.md for .NET 11 Preview 2#10267
jamesmontemagno wants to merge 3 commits intodotnet11-preview2from
dotnet11-preview2-libraries

Conversation

@jamesmontemagno
Copy link
Member

@jamesmontemagno jamesmontemagno commented Feb 17, 2026

Tagging for review:

  • @adamsitnik — Process APIs section (assignee/merger on both #124264 and #124256)
  • @stephentoub — System.Text.Json section (assignee/coauthor/merger on #123940)
  • @iremyux — Tar archive section (assignee/merger on #123407)
  • @kasperk81 — Tar archive section (community author of #123407)
  • @jamesmontemagno — Copilot instructions revised as part of producing these release notes
  • @artl93 — Libraries release notes skill updates made as part of producing these release notes

jeffhandley and others added 2 commits February 20, 2026 02:24
- Add reviewer suggestion step (Step 5) that gathers PR authors, assignees,
  mergers, and coauthors to suggest release notes reviewers grouped by area
- Add feature grouping guidance to categorize related PRs under single sections
- Add positive tone guidelines to editorial rules
- Add issue/PR reference format rules: {org}/{repo}#{number} with markdown links
- Add copilot-instructions.md entry so future sessions discover the skill
- Update data collection and enrichment steps to populate reviewers table
- Exclude bots and Copilot from all reviewer suggestions including coauthors

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
New features: ProcessExitStatus, PosixSignal.SIGKILL, TarFile format
selection, and JsonSerializerOptions.GetTypeInfo<T>().

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@kasperk81
Copy link

Given the volume of PRs in runtime repo, manually calling out API changes will generate a lot of noise and redundant mentions. dotnet/docs already has automation to track new API surface, so this likely isn’t needed.

@jeffhandley
Copy link
Member

Thanks, @kasperk81; that makes sense. I've tuned the skill instructions such that it won't call out all API changes, but it will highlight high-value feature additions delivered through new APIs--like your TarFile contribution. I appreciate you reviewing this too.


### PosixSignal.SIGKILL

[dotnet/runtime#124256](https://github.com/dotnet/runtime/pull/124256) adds `PosixSignal.SIGKILL` to the `PosixSignal` enum, enabling the new process APIs to send and represent SIGKILL signals. SIGKILL cannot be caught or ignored per POSIX semantics — the OS enforces this naturally, throwing appropriate exceptions if registration is attempted. This supports `SafeChildProcessHandle.SendSignal` and `Kill` methods in the upcoming `ChildProcess` API ([dotnet/runtime#123380](https://github.com/dotnet/runtime/issues/123380)).
Copy link
Member

Choose a reason for hiding this comment

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

This feature is useless as of Preview 2 because you can't handle SIGKILL and the API to send a PosixSignal hasn't yet been added. I don't think it's worth calling out.

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.

5 participants