Conversation
* Tidying up CHANGES.txt again to make it easier to edit and copy over to GitHub releases. * Correcting some of the dates to match their respective commits.
DD/MM/YY or MM/DD/YY = confusing. Change to more readable format.
Collaborator
|
Agreed, this is much better I think. Nice work @jamesleesaunders |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While sorting out the 'Releases' and tags for versions (see https://github.com/nioinnovation/python-xbee/releases) I re-formatted the bullet points in CHANGES.txt again so I could easily copy and paste them over into the release notes, after I did this I thought this is actually a better format and easier to maintain so thought I'd pop it out for PR. What do you think?