-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Update changelog's data ranges #11027
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
Conversation
r? @Manishearth (rustbot has picked a reviewer for you, use r? to override) |
@bors r+ |
Update changelog's data ranges Related to #10847 Instead of the non-descriptive commit ranges, now the changelog uses dates (much more illustrative, and cooler 😎 ) changelog:none
💥 Test timed out |
I'll wait for flip's comments to be addressed |
@@ -56,6 +56,29 @@ and open that file in your editor of choice. | |||
When updating the changelog it's also a good idea to make sure that `commit1` is | |||
already correct in the current changelog. | |||
|
|||
#### From commit range to PR link | |||
|
|||
Raw commit ranges aren't used, they aren't very useful or illustrative, so we developed the concept of PR ranges to help the user understand the size of a new update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm, it's less useful to mention the old model here.
Let's just document what we do, rather than what we used to do
@bors r+ |
Update changelog's data ranges Related to #10847 Instead of the non-descriptive commit ranges, now the changelog uses dates (much more illustrative, and cooler 😎 ) changelog:none
💔 Test failed - checks-action_remark_test |
|
@bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Related to #10847
Instead of the non-descriptive commit ranges, now the changelog uses dates (much more illustrative, and cooler 😎 )
changelog:none