dotnet / runtime

Project board to track progress on API and Package Compatibility efforts

Track copying MS Docs documentation to triple slash.

Project that tracks the triaging and execution of PR and issues for the following areas

• area-Microsoft.Win32
• area-System.Diagnostics.EventLog
• area-System.Diagnostics.PerformanceCounter
• area-System.Diagnostics.Tracing
• area-System.Management" area-System.ServiceProcess

Project that tracks the triaging and execution of PR and issues for the team IoT pod (Krzysztof, Buyaa, and Jose).

Issues and PRs from:

• area-Meta
• area-System.CodeDom
• area-System.ComponentModel.Composition
• area-System.Composition
• area-System.Configuration
• area-System.DirectoryServices
• area-System.Reflection
• area-System.Reflection.Emit
• area-System.Reflection.Metadata
• area-System.Resources
• area-System.Runtime.CompilerServices
• area-System.Xml

Issues from:

• System.IO.Compression
• System.IO.Packaging

Tracks work for iOS & Android

Tracks issues and PRs for API triple slash documentation introduced in previous .NET versions.

For tracking .NET Core CodeGen issues

Tracks Stream issues, excluding FileStream.

No description

Packages and Installers

Please see https://github.com/dotnet/runtime/issues/30740 for more background info and discussion on this project.

There is a long list of analyzers and fixers that would provide value. For .NET 5.0, we are favoring analyzers/fixers that meet the following criteria:

• Does the analyzer apply to APIs new in .NET 5.0 or another relatively recent .NET release?
• Is there broad benefit to our teams and the community?
• Is there a relatively low cost?
• Is it possible to create a fixer?
• Is the analyzer a good one for someone with no analyzers experience to "warm up" with?

Tracks File system enumeration work items.

Tracks Pipe Stream (Named/Anonymous, Client/Server) work items.

Tracks Globbing related work items.

Tracking Path, File/Directory, FileInfo/DirectoryInfo/FileSystemInfo related work items.

Excludes:

• File Links - hard links, symbolic links, junctions.
• Globbing.
• Enumeration.

Tracking work items for hard links, symbolic links and junctions support.

Tracking Serial communication related work items.

Tracking FileStream work items.

Excludes all other streams.

Tracking FileSystemWatcher work items.

For tracking issues related to enterprise scenarios such as Negotiate/Kerberos/NTLM authentication on servers and/or proxies.

This project tracks the work that needs to be done in order to support ICU on Windows

Implementation of IETF RFC 8152, along with appropriate extensions (such as IETF RFC 8230 (RSASSA-PSS, RSAES-OAEP)) and prerequisites (such as IETF RFC 7049 (CBOR: Concise Binary Object Representation).

Issues tracking the issue items related to Microsoft.Extensions projects in dotnet/runtime.

Project for managing the infrastructure requirements of the repository. This includes items impacting CI, official builds, partners and local developer workflow.

For tracking issues pertaining to SocketsHttpHandler HTTP2 feature completeness

Docs that describe contribution and developer workflow.

This projects tracks the work for supporting hardware intrinsics in libraries and runtime. See also https://github.com/dotnet/designs/blob/master/accepted/2018/platform-intrinsics.md.

Work to make CoreFX more trimmable and otherwise optimized for the linker.

Work related to improving ML on .NET Core