Re: [VOTE] Release Apache MINA SSHD 2.13.1
+1 Built 'mvn clean verify' the from src zip (ASC OK, SHA512 OK) using: Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) Maven home: C:\java\apache-maven-3.9.8 Java version: 17.0.11, vendor: Eclipse Adoptium, runtime: C:\Program Files\Eclipse Adoptium\jdk-17.0.11.9-hotspot Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Gary On 2024/06/20 20:58:19 Guillaume Nodet wrote: > Hey, > > I've staged a candidate release for an SSHD 2.13.1 release. > This release does not contain any code changes, the only commit is to fix > the release process. The 2.13.0 has reached central, but it did not contain > any source jar. > > *Given this release does not contain any code change, the vote period > will be reduced to 24 hours.* > > Official staging repo: > https://dist.apache.org/repos/dist/dev/mina/sshd/2.13.1/ > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachemina-1095 > Git tag: > https://github.com/apache/mina-sshd/commits/sshd-2.13.1 > > Please review and vote ! > > -- > > Guillaume Nodet > - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[VOTE] Release Apache MINA SSHD 2.13.1
Hey, I've staged a candidate release for an SSHD 2.13.1 release. This release does not contain any code changes, the only commit is to fix the release process. The 2.13.0 has reached central, but it did not contain any source jar. *Given this release does not contain any code change, the vote period will be reduced to 24 hours.* Official staging repo: https://dist.apache.org/repos/dist/dev/mina/sshd/2.13.1/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachemina-1095 Git tag: https://github.com/apache/mina-sshd/commits/sshd-2.13.1 Please review and vote ! -- Guillaume Nodet
Re: Missing source files for SSHD 2.13.0 release
Le jeu. 20 juin 2024 à 17:54, Emmanuel Lécharny a écrit : > Can't you just cancel the 2.13.1 and redo the exact same release? > 2.13.0 has been published to maven central. That's how someone saw the problem, after being synced to central. So I need to do a 2.13.1. > 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). > Yeah, good idea. I'll try to do that asap. Guillaume > > > 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 > elecha...@apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org > For additional commands, e-mail: dev-h...@mina.apache.org > > -- Guillaume Nodet
Re: Missing source files for SSHD 2.13.0 release
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 elecha...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
