+1 Checks performed: - Verified SHA512 checksum: OK - Verified GPG
signature: Good signature from Thomas Wolf - LICENSE.txt and NOTICE.txt
present - No binary files in source archive - No .git directory in source
archive - Apache RAT check (license headers): OK - Build from source with
./mvnw clean verify -DskipTests
: BUILD SUCCESS (all 19 modules) - CHANGES.md reviewed Minor observations
(non-blocking): 1. NOTICE.txt copyright year says "2008-2021", could be
updated to "2008-2026" 2. CHANGES.md line 12 has a stray '+' character:
+[commit a3d22510]
should be
[commit a3d22510]
3. CHANGES.md heading for Milestone 3 uses
#
(h1) while Milestones 1 and 2 use
##
(h2)

Guillaume

Le dim. 15 mars 2026 à 22:02, Thomas Wolf <[email protected]> a écrit :

> Hello,
>
> I've staged a candidate for a new milestone pre-release 3.0.0-M3.
>
> This is a minor update to bring the improvements done in 2.17.x into
> the 3.0.0 stream. Besides that, there is only one tiny bug fix from
> 3.0.0-M2.
>
> Due to vacations in November and in February and due to the Christmas
> season in between work on 3.X stalled a bit, and moreover some of the
> things I had planned for 3.X actually got done in 2.17.0. Hence this
> new pre-release milestone bringing the 2.17.x improvements to 3.0.0.
>
> Official staging repo:
>    https://dist.apache.org/repos/dist/dev/mina/sshd/3.0.0-M3/
> Maven staging repo:
>    https://repository.apache.org/content/repositories/orgapachemina-1131
>
>
> Git tag:
>    https://github.com/apache/mina-sshd/commits/sshd-3.0.0-M3
> Change notes:
>    https://github.com/apache/mina-sshd/blob/sshd-3.0.0-M3/CHANGES.md
>
>
> Apache MINA KEYS file:
>    https://downloads.apache.org/mina/KEYS
>
> The SHA512 checksum files have been created with 'shasum -a512 -b'.
>
> Please review and vote!
>
> Cheers,
>
>    Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
------------------------
Guillaume Nodet

Reply via email to