Skip to content

docs: update license year range to 2024 #5890

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.

Sign up for GitHub

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

Jump to bottom
Merged
PastaPastaPasta merged 1 commit into from
Feb 23, 2024
Merged

docs: update license year range to 2024 #5890

PastaPastaPasta merged 1 commit into from
Feb 23, 2024

Conversation

@knst
Copy link
Collaborator

@knst knst commented Feb 21, 2024

What was done?

Happy new year and happy new lunar year!
2024 is here and 20.1 is coming.

Breaking Changes

N/A

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone

@knst knst added this to the 20.1 milestone Feb 21, 2024
@knst knst changed the title doc: Update license year range to 2024 docs: Update license year range to 2024 Feb 21, 2024
@knst knst changed the title docs: Update license year range to 2024 docs: update license year range to 2024 Feb 21, 2024
@PastaPastaPasta
Copy link
Member

PastaPastaPasta commented Feb 21, 2024

Should run https://github.com/dashpay/dash/blob/develop/contrib/devtools/copyright_header.py as well

@PastaPastaPasta
Copy link
Member

PastaPastaPasta commented Feb 21, 2024 •
edited
Loading

Removed "backport candidate" as that is (currently) for v20.0.5 theoretically; not v20.1; develop is still v20.1

@knst
Copy link
Collaborator Author

knst commented Feb 21, 2024

Removed "backport candidate" as that is (currently) for v20.0.5 theoretically; not v20.1; develop is still v20.1

I added a label for possible v20.0.5 if any between release would be done

@PastaPastaPasta
Copy link
Member

PastaPastaPasta commented Feb 21, 2024

Removed "backport candidate" as that is (currently) for v20.0.5 theoretically; not v20.1; develop is still v20.1

I added a label for possible v20.0.5 if any between release would be done

hmmm yeah; but I don't think this is worth backporting even if we do need v20.0.5, unless you want to do a new PR that runs the copyright bump instead of in this PR

PastaPastaPasta
PastaPastaPasta approved these changes Feb 21, 2024
View reviewed changes
Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK for squash merge

@knst
Copy link
Collaborator Author

knst commented Feb 21, 2024

unless you want to do a new PR that runs the copyright bump instead of in this PR

#5892

A notice for next year: copyright year for sources should be bumped at the end of year next time; license year is preferred to bump after NY

UdjinM6
UdjinM6 approved these changes Feb 22, 2024
View reviewed changes
Copy link

@UdjinM6 UdjinM6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@PastaPastaPasta PastaPastaPasta merged commit c75fff6 into dashpay:develop Feb 23, 2024
@knst knst deleted the fix-copyright-year branch February 23, 2024 18:25
@knst knst mentioned this pull request Jan 4, 2026
Merged
5 tasks
PastaPastaPasta added a commit that referenced this pull request Jan 20, 2026
@PastaPastaPasta
Merge #7087: chore: Update license year range to 2026
69ff3a3 
796a844 doc: Update license year range to 2026 (Konstantin Akimov)

Pull request description:

  ## What was done?

  Annual copyright bump. Prior PRs: #5890, #6546

  ## How Has This Been Tested?
  N/A

  ## Breaking Changes
  N/A

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  UdjinM6:
    utACK 796a844

(should probably be `chore`, not `doc`)
  kwvg:
    utACK 796a844

Tree-SHA512: fd3406a7261f16b24c1d16b05591358dc7ed4d54e238b4a1f8d5cd3ab30888c84565361334774b7eaee0c3ae60d34d468e778ec29bf66cabe86dcf26ed341afc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@UdjinM6 UdjinM6 UdjinM6 approved these changes

@PastaPastaPasta PastaPastaPasta PastaPastaPasta approved these changes

@thephez thephez Awaiting requested review from thephez

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

20.1

Development

Successfully merging this pull request may close these issues.

3 participants

@knst @PastaPastaPasta @UdjinM6