vinishjail97 opened a new pull request, #874:
URL: https://github.com/apache/incubator-xtable/pull/874

   ## What
   
   Backport of #873 to `branch-0.4` so that 0.4.0-incubating RC2 ships a 
correct `NOTICE`.
   
   Refs #872
   
   ## Why
   
   "Checked NOTICE file content and distribution years" was one of the `[KO]` 
items in the [0.4.0-incubating RC1 
vote](https://lists.apache.org/thread/pjl0xgfns56bx219494oc51qnj2mll8b). RC2 is 
cut from this branch, so the fix has to land here, not only on `main`.
   
   The root `NOTICE` said `Copyright 2024-2025` while the release is being made 
in 2026. The `NOTICE` inside the jars is generated by 
`maven-remote-resources-plugin` and already said `2024-2026`, so the source 
release and the convenience binaries disagreed.
   
   ## Changes
   
   Identical to #873, cherry-picked, applied cleanly since both files matched 
across branches:
   
   - `NOTICE`: copyright range `2024-2025` to `2024-2026`.
   - `release/scripts/validate_source_copyright.sh`: also verify the copyright 
line is well formed, starts at the `pom.xml` `<inceptionYear>`, and ends at the 
year the release is being cut. Invoked from `validate_staged_release.sh`, so a 
stale `NOTICE` now fails release validation rather than surfacing during a 
vote. #692 fixed the same drift by hand for 2025 with nothing to stop it 
recurring.
   
   ## Testing
   
   Same matrix as #873. Accepts `2024-2026`, rejects `2024-2025` (what RC1 
shipped), a bare `2024`, a wrong start year, and a malformed line. Verified 
against the real `NOTICE` and `pom.xml` on this branch, reports `[OK]` and 
exits 0.


-- 
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]

Reply via email to