docs: update NOTICE copyright to "2025 and onwards"#5158
Open
bobbai00 wants to merge 1 commit into
Open
Conversation
Avoids needing yearly updates by following Apache Spark's practice.
Contributor
|
let's delay merging this one, till we figure out which branch to include it. |
| @@ -1,5 +1,5 @@ | |||
| Apache Texera (Incubating) | |||
| Copyright 2025 The Apache Software Foundation | |||
| Copyright 2025 and onwards The Apache Software Foundation | |||
Contributor
There was a problem hiding this comment.
better to be "2026 and onwards"?
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.
What changes were proposed in this PR?
Updates the copyright line in
NOTICE(and the duplicate atbin/single-node/NOTICE) fromCopyright 2025 The Apache Software FoundationtoCopyright 2025 and onwards The Apache Software Foundation.Following Apache Spark's practice — avoids needing to bump the year on every release.
Any related issues, documentation, discussions?
Closes #5157
How was this PR tested?
Doc-only change; no tests required.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7 (1M context)