xxubai opened a new pull request, #4365:
URL: https://github.com/apache/amoro/pull/4365
## Why are the changes needed?
The Apache Amoro NOTICE metadata is inconsistent with the project release
history and the 2026 release cycle. The source and binary NOTICE files still
use 2025, the binary NOTICE preamble uses 2024, and the Maven output timestamp
causes generated JAR NOTICE files to retain the old year.
## Brief change log
- Update the Amoro copyright range in `NOTICE`, `NOTICE-binary`, and the
binary NOTICE preamble to `2024-2026`.
- Update `project.build.outputTimestamp` to `2026-09-08T00:00:00Z` so
Maven-generated NOTICE files use the same range.
- Keep all third-party copyright years unchanged.
## How was this patch tested?
- [ ] Add some test cases that check the changes thoroughly including
negative and positive cases if possible
Not applicable because this patch only updates release metadata.
- [ ] Add screenshots for manual tests if appropriate
Not applicable because there is no UI change.
- [x] Run test locally before making a pull request
- Built the `dist` dependency closure successfully with 20/20 Maven
modules passing.
- Verified `META-INF/NOTICE` in a regular JAR and a shaded JAR contains
`Copyright 2024-2026 The Apache Software Foundation`.
- Verified the release-layout binary tar contains exactly one top-level
NOTICE with the same Amoro copyright range.
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
