Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M10
On 10/26/22 12:47, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M10-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1248 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352341 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1248 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M10 org.apache.qpid protonj2-client 1.0.0-M10 +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified license headers in source tree using 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an Artemis broker install -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Fwd: Migrating away from Travis-CI
FYI for anyone who didnt see the original message, Infra will be creasing the remaining support for TravisCI usage going forward, deadline Dec 31st. The following repositories still have Travis build configs that will need either removed or migrated (many already use multiple CI envs so probably mainly the former) by Dec 31st: qpid-proton qpid-cpp qpid-dispatch qpid-jms qpid-broker-j qpid-proton-j I'll probably just leave qpid-jms and qpid-proton-j ones in place until December and then remove. -- Forwarded message - From: Drew Foulks Date: Mon, 24 Oct 2022 at 22:43 Subject: Migrating away from Travis-CI To: Greetings PMC Members! Infrastructure is moving away from Travis-CI at the end of 2022. If your project is not currently using Travis-CI, this email is not actionable. Projects using Travis-CI: Please take a look at https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations and join the builds meetings and mailing list for project updates. -- Cheers, Drew Foulks ASF Infra - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M10
Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M10-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1248 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352341 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1248 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M10 org.apache.qpid protonj2-client 1.0.0-M10 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M5
On Mon, Oct 24, 2022 at 7:15 PM Timothy Bish wrote: > Hi folks, > > I have put together a release candidate for a 1.0.0-M5 Qpid > proton-dotnet release, > please give it a test out and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M5-rc1/ > > The JIRAs assigned are: > https://issues.apache.org/jira/projects/PROTON/versions/12352342 > > Regards > > -- > Tim Bish > +1 1. downloaded sources directory 2. ran ./build.sh podman-test on Fedora 37 beta in the sources directory, no tests failed -- Mit freundlichen Grüßen / Kind regards Jiri Daněk