Skip to content

Commit 6f0fae3

Browse files
committed
Minor fixes and date correction to book page
1 parent d369dc2 commit 6f0fae3

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

book/src/development/feature_freeze.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,20 @@
22

33
This is a temporary notice.
44

5-
From May 9th, 2025 until the 1st of August, 2025 we will perform a feature freeze. Only bugfix PRs will be reviewed
6-
with the exception of already open ones. Every feature-adding PR opened in between those dates will be moved into a
5+
From the 26th of June until the 18th of September we will perform a feature freeze. Only bugfix PRs will be reviewed
6+
except already open ones. Every feature-adding PR opened in between those dates will be moved into a
77
milestone to be reviewed separately at another time.
88

99
We do this because of the long backlog of bugs that need to be addressed
10-
in order to contiue being the state of the art linter that Clippy has become known for being.
10+
in order to continue being the state-of-the-art linter that Clippy has become known for being.
1111

1212
## For contributors
1313

1414
If you are a contributor or are planning to become one, **please do not open a lint-adding PR**, we have lots of open
1515
bugs of all levels of difficulty that you can address instead!
1616

1717
We currently have about 800 lints, each one posing a maintainability challenge that needs to account to every possible
18-
usecase of the whole ecosystem. Bugs are natural in every software, but the Clippy team considers that Clippy needs a
18+
use case of the whole ecosystem. Bugs are natural in every software, but the Clippy team considers that Clippy needs a
1919
refinement period.
2020

2121
If you open a PR at this time, we will not review it but push it into a milestone until the refinement period ends,
@@ -33,14 +33,14 @@ debugging, sometimes interacting directly with the upstream compiler. Difficult
3333
improves a lot developer workflows!
3434

3535
- 🟧 [Suggestion causes bug][sugg_causes_bug], Clippy suggested code that changed logic in some silent way.
36-
Unacceptable, as this may have disastreous consequences. Easier to fix than ICEs
36+
Unacceptable, as this may have disastrous consequences. Easier to fix than ICEs
3737

3838
- 🟨 [Suggestion causes error][sugg_causes_error], Clippy suggested code snippet that caused a compiler error
3939
when applied. We need to make sure that Clippy doesn't suggest using a variable twice at the same time or similar
4040
easy-to-happen occurrences.
4141

4242
- 🟩 [False positives][false_positive], a lint should not have fired, the easiest of them all, as this is "just"
43-
identifying the root of a the false positive and making an exception for those cases.
43+
identifying the root of a false positive and making an exception for those cases.
4444

4545
Note that false negatives do not have priority unless the case is very clear, as they are a feature-request in a
4646
trench coat.

0 commit comments

Comments
 (0)