Update copyright years in NOTICE.txt file.#493
Merged
cpoerschke merged 3 commits intoapache:mainfrom Jan 26, 2022
Merged
Conversation
Contributor
|
Happy New Year! Hehe, as the Lucene NOTICE text does not mention a specific Lucene release, I'd update it right away. |
Contributor
Author
Done. |
Contributor
Author
|
@janhoy is it okay to merge and backport this to branch_9_0 also? |
janhoy
approved these changes
Jan 25, 2022
asfgit
pushed a commit
that referenced
this pull request
Jan 26, 2022
(cherry picked from commit af9f3c3)
asfgit
pushed a commit
that referenced
this pull request
Jan 26, 2022
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
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.
Happy New Year 2022!
Opening this tiny pull request for extra perspectives on when to update the line 139 copyright year:
versions.propsupdates to a non-2021 Lucene version, or