Update Copyright to 2020 #1524
Milestone
Comments
|
If it's a task of next release, one PR to develop branch is enough, since it will be merged into other branches later. If we want to have it in master branch before next release (which IMHO is not needed because we haven't contributed code to master in 2019 so no need to update license year there), please follow the document-change steps (aka Emergency Fix steps) listed in Git Flow. |
|
Yes, you are correct @abitmore we need only #1525 and it will propagate elsewhere. @xeroc provided a thoughtful comment #1525 (comment) for me to consider, so moving this to the next Feature Release. |
|
Done. #1525. |
abitmore
modified the milestones:
4.1.0 - Feature Release,
4.0.0 - Protocol Upgrade Release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
As the
BitShares DACwe wantthe copyright to reflect the current yearso thatour development efforts are respected.Additional Context (optional)
Impacts multiple branches:
- [ ]master#1523developUpdate copyright for 2020 #1525- [ ]hardforkUpdate copyright for 2019 (hardfork) #1526The text was updated successfully, but these errors were encountered: