Add linker working area in our docs

src/compiler/operations.md

@@ -67,6 +67,7 @@ First, ensure that relevant issues are labelled as `T-compiler`:
 - [Issues labeled `I-compiler-nominated`](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AI-nominated+-label%3AT-compiler+-label%3AT-cargo+-label%3AT-core+-label%3AT-doc+-label%3AT-infra+-label%3AT-lang+-label%3AT-libs+-label%3AT-libs-api+-label%3AT-release+-label%3AT-rustdoc+-label%3AA-rustdoc+-label%3AA-rustdoc-ui) (i.e. needing a T-compiler discussion)
 - [Pull requests waiting on a team's feedback](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AS-waiting-on-team+-label%3AT-compiler+-label%3AT-cargo+-label%3AT-core+-label%3AT-doc+-label%3AT-infra+-label%3AT-lang+-label%3AT-libs+-label%3AT-libs-api+-label%3AT-release+-label%3AT-rustdoc+-label%3AA-rustdoc+-label%3AA-rustdoc-ui)
 - [Issues classified with priority `P-high`](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AP-high+-label%3AT-compiler+-label%3AT-cargo+-label%3AT-core+-label%3AT-doc+-label%3AT-infra+-label%3AT-lang+-label%3AT-libs+-label%3AT-libs-api+-label%3AT-release+-label%3AT-rustdoc+-label%3AA-rustdoc+-label%3AA-rustdoc-ui)
+- [Issues classified with priority `P-critical`](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AP-critical+-label%3AT-compiler+-label%3AT-cargo+-label%3AT-core+-label%3AT-doc+-label%3AT-infra+-label%3AT-lang+-label%3AT-libs+-label%3AT-libs-api+-label%3AT-release+-label%3AT-rustdoc+-label%3AA-rustdoc+-label%3AA-rustdoc-ui)
 
 ..and that prioritization has been completed. Regressions labeled with `I-prioritize` are signaling
 that a priority assessment is waiting. When this label is added to an issue, the `triagebot` sends a

src/compiler/working-areas.md

@@ -9,10 +9,11 @@ Diagnostics                       | Use crates.io crates for diagnostics renderi
 LLVM                              | Working with LLVM upstream to represent Rust in its development                                    | [rustc], [LLVM][llvm_code]                                                  | [#t-compiler/llvm][llvm_stream]
 MIR Optimizations                 | Write MIR optimizations and refactor the MIR to be more optimizable.                               | [MIR transform][mir_transform_code]                                         | [#t-compiler/mir-opts][mir-opts-stream]
 Parallel-rustc                    | Making parallel compilation the default for rustc                                                  | [rustc]                                                                     | [#t-compiler/parallel-rustc][parallel-rustc_stream]
-Polonius                          | Exploring the integration of the "NLL 2.0"-like ["Polonius analysis"][Polonius] into rustc         | [borrow check][borrowck], [rust-lang/polonius][P], [rust-lang/datafrog][DF] |  [#t-types/polonius][polonius_stream]
+Polonius                          | Exploring the integration of the "NLL 2.0"-like ["Polonius analysis"][Polonius] into rustc         | [borrow check][borrowck], [rust-lang/polonius][P], [rust-lang/datafrog][DF] | [#t-types/polonius][polonius_stream]
 RLS 2.0                           | Experimenting with a new compiler architecture tailored for IDEs                                   | [rust-analyzer][ra-repo]                                                    | [#t-compiler/rust-analyzer][rls20_stream]
 Rust Compiler Development Guide   | Make the compiler easier to learn by ensuring that rustc-dev-guide is "complete"                   | [rustc], [rustc-dev-guide][rustc-dev-guide-repo]                            | [#t-compiler/rustc-dev-guide][rustc-dev-guide_stream]
-Enzyme                            | Expose experimental LLVM features for GPU offloading                                               | [Project Goal][enzyme-project-goal] | [#wg-autodiff]
+Enzyme                            | Expose experimental LLVM features for GPU offloading                                               | [Project Goal][enzyme-project-goal]                                         | [#wg-autodiff]
+Linker                            | Helping deal with linker related issues and their integration within the compiler                  | -                                                                           | [#wg-linker]
 
 For historical record here's a list of Working Groups that are not active anymore (either because they reached their goals or because work stalled):
 
@@ -62,3 +63,4 @@ Traits                           | Improving the trait-system design + implement
 [annotate-snippets]: https://crates.io/crates/annotate-snippets
 [#wg-autodiff]: https://rust-lang.zulipchat.com/#narrow/channel/390790-wg-autodiff
 [enzyme-project-goal]: https://github.com/rust-lang/rust-project-goals/issues/109
+[#wg-linker]: https://rust-lang.zulipchat.com/#narrow/channel/585172-t-compiler.2Flinker

src/release/backporting.md

@@ -1,6 +1,6 @@
 # Backporting
 
-> ## What is a backport?
+## What is a backport?
 
 > A **backport** is the act of taking a fix or feature that landed in a newer Rust release
 > (or any software) and re-applying it to an older supported branch. This is most often used