Update website copyright year to 2023#5787
Merged
vlsi merged 1 commit intoapache:masterfrom May 19, 2023
Merged
Conversation
Do we really need the year here?
|
Just nitpicking a little - if a repo was not updated (yet) in 2023 -- there is no need to update the (c) statement either. E.g. (c) 1990-2023 implies that in each of those 13 years somethings copyright worthy (i.e change & release under license) was done. That is why you sometimes see odd (c) 1990-2003,2005-2021,2023 sort of lines. |
Member
Author
|
True (see also https://apache.org/legal/src-headers.html#notice) - it looks like there's been plenty of copyrightable commits to the repo in 2023 already though, so an update does seem due |
Contributor
|
We usually update the website, when we do a release (which we haven't done yet, this year). |
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
4 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.
Description
Update the copyright year in the NOTICE, which also affects the website.
Motivation and Context
Do we really need the year here?
How Has This Been Tested?
./gradlew buildPreviewSite