On Sun, Mar 15, 2026 at 2:05 PM Henri Biestro <[email protected]> wrote: > > [+1] > > Build & tests ok; site & javadoc look good; reports check. > > Nits: many changes without JIRA tickets, hard to track what the changes > actually are; should we have at least a commit # in the reports somehow ?
Hi Henri, Changes are listed in changes.xml, which gets transformed into the release notes [1] and the HTML changes report page [2]: [1] https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/RELEASE-NOTES.txt [2] https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/site/changes.html#a3.13.0 HTH, Gary > > Verified with: mvn clean install site -s "$HOME/.m2/commons-settings.xml" > On: mvn -version > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /Users/hbiestro/Java/apache-maven-3.8.6 > Java version: 17.0.18, vendor: Azul Systems, Inc., runtime: > /Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.3.1", arch: "aarch64", family: "mac" > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
