snoopdave opened a new pull request, #179:
URL: https://github.com/apache/roller/pull/179

   Two pieces of release preparation.
   
   ## Third-party jars removed from the source distribution
   
   The source release carried four compiled third-party jars under 
`docs/examples/scripting/`:
   
   - `bsf/lib/bsf.jar`
   - `groovy/examples/adminprotocol/lib/roller-rap-sdk.jar`
   - `groovy/examples/adminprotocol/lib/commons-codec-1.3.jar`
   - `groovy/examples/adminprotocol/lib/jdom.jar`
   
   A source release should carry source. None of the four appear in `LICENSE` 
or `NOTICE`, so they were also unaccounted for, and `commons-codec-1.3` and 
`bsf.jar` are old enough that nobody currently active chose them.
   
   The two README files that told readers to use these jars now say to obtain 
them separately; the classpath examples are otherwise unchanged. Nothing in the 
build referenced them — the assembly descriptor takes `docs/` wholesale rather 
than naming them.
   
   After this change `docs/` contains no `.jar`, `.war` or `.class` files at 
all.
   
   ## CHANGES.md
   
   There was no release notes file in the repo, so the vote and announcement 
had nothing to point at. This adds one, starting at 6.1.6; earlier notes stay 
in the mailing list archive.
   
   It leads with the three retirements that need action before upgrading — 
incoming Trackback, outbound Trackback, and WSSE AtomPub authentication, the 
last of which now fails closed on startup rather than falling back — followed 
by the media content type and enclosure metadata behaviour changes, then the 
rest.
   
   ## Verification
   
   Full suite on JDK 11: **297 tests, 0 failures, 0 errors, 1 skipped**.
   
   https://claude.ai/code/session_019R1jdtwkaYEeA6L9DXEtEi


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