diff options
| author | Philipp Krones <hello@philkrones.com> | 2025-06-26 16:45:13 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-26 16:45:13 +0000 |
| commit | 8050e591b6db92d8c1df55994415b1acfaf1d150 (patch) | |
| tree | f747e384ff7ed4e0579df88243559ce943100a69 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 40554ef4aa6f92f166f8b19e3d999e6e93505d16 (diff) | |
| parent | b88d162d2afd3f65d90b84f8bad1793858ecfe8c (diff) | |
| download | rust-8050e591b6db92d8c1df55994415b1acfaf1d150.tar.gz rust-8050e591b6db92d8c1df55994415b1acfaf1d150.zip | |
Update book and templates with feature freeze (#14456)
This PR announces the feature freeze period talked about in https://github.com/rust-lang/rust-clippy/issues/14364 1. Add the page to the book 2. Modify the in-Github templates. 3. The third commit (to be squashed into the first) rolls the date mentioned 6 weeks (so, starting on May 9th and ending on August 20th). This gives us a comfortable buffer to make choices for this period. We have a pending discussion on the #14364. So having some more time to make choices is very nice. I'm also preparing a Github action for detecting new lints and posting a comment about the feature freeze (being worked on in another branch) Something I'd like comment on is the date formatting. I'm not sure if "May 9th to the first of August" is the correct way of writing this information in a book :sweat_smile:. changelog: Announce the feature freeze from May 9th to the first of August
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
