add changelog for 3.41.3#183030
add changelog for 3.41.3#183030auto-submit[bot] merged 1 commit intoflutter:flutter-3.41-candidate.0from
Conversation
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
![gemini-code-assist[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the changelog for the 3.41.3 hotfix. My review focuses on ensuring the changelog entries adhere to the project's documentation best practices. I've suggested a minor wording change to one of the entries to better describe the problem being solved, rather than the fix itself, for improved clarity for users.
|
|
||
| ### [3.41.3](https://github.com/flutter/flutter/releases/tag/3.41.3) | ||
|
|
||
| - [flutter/182501](https://github.com/flutter/flutter/issues/182501) Reduce CPU utilization of idle Flutter Windows apps. |
There was a problem hiding this comment.
According to the Hotfix Documentation Best Practices, changelog entries for hotfixes should describe the problem from the user's perspective, not the fix itself. This entry describes what the fix does, rather than the problem it solves.
To improve clarity for users scanning the changelog, please rephrase this to describe the issue that was fixed.
| - [flutter/182501](https://github.com/flutter/flutter/issues/182501) Reduce CPU utilization of idle Flutter Windows apps. | |
| - [flutter/182501](https://github.com/flutter/flutter/issues/182501) Idle Flutter apps on Windows may exhibit high CPU utilization. |
References
- Hotfix changelog entries should describe the problem from the user's perspective, not the fix. The recommended format is 'When [scenario] [on platform], [problem description]'. The current entry describes the fix ('Reduce CPU utilization...'). This guidance is from
docs/releases/Hotfix-Documentation-Best-Practices.md, which is referenced in the repository style guide. (link)
reidbaker
added
the
autosubmit
auto-submit
bot
merged commit 48c32af
into
flutter:flutter-3.41-candidate.0
2 participants
Only 2 non test cherry picks for stable since 3.41.2 https://github.com/flutter/flutter/pulls?q=is%3Apr+base%3Aflutter-3.41-candidate.0+is%3Aclosed
#182864
#182691