Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Clean changelog. Bump to version: 3.5.0
- Loading branch information
Showing
1 changed file
with
14 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0c88697
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.
Thanks for updating the changelog and releasing. What do you think about using this changelog format?
http://keepachangelog.com/
I think it's a little easier to work with and conveys the same or more information.
0c88697
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.
I do like the inclusion of the date next to the version number, but other than that I feel like I don't get as much information at a glance as I do with the existing format. The current version really emphasizes "this release consists mostly of [BUGFIX]", and the vertical lines from the quote-block elements help distinguish releases. In the new version, the bullets start to blend together a little bit and I have to check what header something falls under.
Sorry for reverting the formatting on you, but the inconsistency confused me. If we experiment with a new format I think we should rewrite the changelog once we decide, so everything looks the same.
0c88697
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.
I agree the at-a-glance view is not as concise. However, for the ease of pointing people to http://keepachangelog.com/ I would like to follow that document going forward. While it would be nice to update all past changelog entries, I do not see that as a requirement to impose the new format going forward.
With that said we could only use the new format with everything >= 4.0.
0c88697
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.
Starting the new format in PRAW4+ sounds like a fair compromise. Are there any design elements you would be comfortable adding, to improve readability without deviating too far from the keepachangelog structure? Even small things like the blockquote line really help visually compartmentalize each release. If we both feel that the kacl structure is less immediately clear than it could be, I think that's a good sign that some customization is worthwhile.
0c88697
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.
If there is anything you'd like to add, it would probably be nice adding it to
contributing.md
.