-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate the CHANGELOG for webdev and dwds as part of the release process #2083
Conversation
I don't think this type of automation is a good idea. Commit messages and Changelogs have different audiences, and I don't think we should conflate them. |
Oh interesting! This is what DevTools has been doing for a while (see flutter/devtools#5603). What do you see as the difference between commit messages and CHANGELOG? |
This is a good example of why I think it's a bad idea (cc @jacob314 @kenzieschmoll ) This is a very noisy changelog to parse through, with entries that end users don't care about. It's harder to find the changes that are meaningful to the users when they have to scan over stuff like
And over 100 other entries which likely mean nothing to them, before they hit an entry that they may be interested in
|
+1 I would not do this, compare that changelog to the one in package:test https://github.com/dart-lang/test/blob/master/pkgs/test/CHANGELOG.md. This is a far more user centric changelog imo, with only the information that is actually relevant to a consumer of the package. |
Closing in favor of #2090 |
Work towards #2085
The release script auto-populates the CHANGELOG with all of the commits since the last release in the format: