Can't you just cancel the 2.13.1 and redo the exact same release?

In any case, your commit is not a code commit, so voting the release can be quickly done (maybe asking for a 24h vote instead of 3days could help).


On 19/06/2024 21:55, Guillaume Nodet wrote:
During the release, I experienced a problem when trying to close the
staging repository. One of the signature was wrong and nexus did not want
to close the repository.  I ended up bypassing the usual release process
(mvn release:perform) and did a manual deploy.  Unfortunately, I forgot to
build the source jars, so none of the jar has an associated source jar in
maven central.

The problem should have been fixed by my last commit [1].  I don't think
there's a way to deploy just the source jars, so should I cut a 2.13.1
release ?

Cheers,
Guillaume Nodet

[1]
https://github.com/apache/mina-sshd/commit/50d1d9fd2f4d21a22f8eb978a2e4f47c1349e5bb


--
*Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to