Re: [HEADS-UP] ActiveMQ Artemis 2.22.0 next week
I just tagged and the repo is uploaded... feel free to commit on main again... On Wed, Apr 27, 2022 at 8:33 AM Clebert Suconic wrote: > > I had just CTRL-C the mvn -Prelease :P > > > I will go with 2.22.0 > > > Talking of which... please hold today (until I send another note) to > commit on main. > > On Wed, Apr 27, 2022 at 8:32 AM Clebert Suconic > wrote: > > > > yeah.. good point on the default behaviour.. > > > > On Wed, Apr 27, 2022 at 7:05 AM Robbie Gemmell wrote: > > > > > > Looking at what is currently in it, more improvements than bug fixes > > > and some changes in default behaviour, I would go with 2.22.0 > > > personally. > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARTEMIS%20AND%20fixVersion%20%3D%202.22.0%20ORDER%20BY%20issuetype%20DESC > > > > > > On Mon, 25 Apr 2022 at 21:44, Justin Bertram wrote: > > > > > > > > I'm fine with naming it 2.21.1. > > > > > > > > However, if you could hold the release until I fix ARTEMIS-3801 [1]. I hope > > > > to send a PR later today. > > > > > > > > > > > > Justin > > > > > > > > [1] https://issues.apache.org/jira/browse/ARTEMIS-3801 > > > > > > > > On Mon, Apr 25, 2022 at 10:53 AM Clebert Suconic < clebert.suco...@gmail.com> > > > > wrote: > > > > > > > > > Of course I meant you would need a new feature for it to be 2.22.0... > > > > > I only see bug fixes and improvements... > > > > > > > > > > there was one JIRA that was recorded as feature: > > > > > > > > > > https://issues.apache.org/jira/browse/ARTEMIS-3765 > > > > > > > > > > > > > > > and I also consider it an improvement. > > > > > > > > > > > > > > > > > > > > > > > > > if anyone wants it to be named 2.22.0 instead of 2.21.1 please let me know. > > > > > > > > > > On Mon, Apr 25, 2022 at 11:42 AM Clebert Suconic > > > > > wrote: > > > > > > > > > > > > I will call this release 2.21.1... > > > > > > > > > > > > > > > > > > I only see improvements and bug fixes... I think for a 2.22.0 you > > > > > > would need a new JIRA. > > > > > > > > > > > > > > > > > > anyone strongly opinionated about calling it 2.22.0? > > > > > > > > > > > > On Fri, Apr 22, 2022 at 5:34 PM Clebert Suconic > > > > > > wrote: > > > > > > > > > > > > > > cool... I will finish > > > > > > > https://github.com/apache/activemq-artemis/pull/4012 and cut the > > > > > > > release. Hoping monday.. but perhaps tuesday. > > > > > > > > > > > > > > On Fri, Apr 22, 2022 at 4:43 AM Robbie Gemmell < > > > > > robbie.gemm...@gmail.com> wrote: > > > > > > > > > > > > > > > > Sounds like a great idea, I was also starting to think there seemed > > > > > > > > enough important things in there already, and releasing more often > > > > > > > > would definitely be good either way. > > > > > > > > > > > > > > > > On Fri, 22 Apr 2022 at 03:28, Clebert Suconic < > > > > > clebert.suco...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > I will check the payload if that will be a 2.21.1 or a 2.22.0 > > > > > > > > > (depending on new features or not), and make a release early next > > > > > > > > > week. > > > > > > > > > > > > > > > > > > > > > > > > > > > The branch is in nice shape and I would rather cut more often... we > > > > > > > > > could make another one not long after. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > -- > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > -- > > Clebert Suconic > > > > -- > Clebert Suconic -- Clebert Suconic -- Clebert Suconic
Re: [VOTE] Release activemq-nms-api 1.8.1-rc1
On 4/25/22 13:40, Havret wrote: Hi all, I have put together a release of activemq-nms-api, please check it and vote accordingly. This release contains a single bugfix[1] by Iuliia Fatkullina! Thank you! The files can be grabbed from: https://dist.apache.org/repos/dist/dev/activemq/activemq-nms-api/1.8.1-rc1/ Regards, Krzysztof [1]: https://issues.apache.org/jira/browse/AMQNET-745 I took a brief look at the release, the NOTICE file appears to be rather out of date (2019). Haven't looked deeper yet. -- Tim Bish
Re: [VOTE] Apache ActiveMQ 5.17.1 release
+1 (non-binding) - Installed to Karaf 4.3.7 - Ran spot checks - Ran internal test suites Thanks JB! > On Apr 25, 2022, at 9:21 AM, Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit the ActiveMQ 5.17.1 release to your vote. > > This release is an important release on the 5.17.x series, bringing > major changes: > - upgrade to Spring 5.3.19, fixing Spring4shell vulnerability (even if > ActiveMQ is not directly impacted) > - XBean 4.21 (supporting Spring 5.x) and ASM 9.3 for better Java 18+ support > - and much much more > > Please take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351348 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapacheactivemq-1250/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.1/ > > Git tag: activemq-5.17.1 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Thanks ! > Regards > JB
Re: [HEADS-UP] ActiveMQ Artemis 2.22.0 next week
I had just CTRL-C the mvn -Prelease :P I will go with 2.22.0 Talking of which... please hold today (until I send another note) to commit on main. On Wed, Apr 27, 2022 at 8:32 AM Clebert Suconic wrote: > > yeah.. good point on the default behaviour.. > > On Wed, Apr 27, 2022 at 7:05 AM Robbie Gemmell > wrote: > > > > Looking at what is currently in it, more improvements than bug fixes > > and some changes in default behaviour, I would go with 2.22.0 > > personally. > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARTEMIS%20AND%20fixVersion%20%3D%202.22.0%20ORDER%20BY%20issuetype%20DESC > > > > On Mon, 25 Apr 2022 at 21:44, Justin Bertram wrote: > > > > > > I'm fine with naming it 2.21.1. > > > > > > However, if you could hold the release until I fix ARTEMIS-3801 [1]. I > > > hope > > > to send a PR later today. > > > > > > > > > Justin > > > > > > [1] https://issues.apache.org/jira/browse/ARTEMIS-3801 > > > > > > On Mon, Apr 25, 2022 at 10:53 AM Clebert Suconic > > > > > > wrote: > > > > > > > Of course I meant you would need a new feature for it to be 2.22.0... > > > > I only see bug fixes and improvements... > > > > > > > > there was one JIRA that was recorded as feature: > > > > > > > > https://issues.apache.org/jira/browse/ARTEMIS-3765 > > > > > > > > > > > > and I also consider it an improvement. > > > > > > > > > > > > > > > > > > > > if anyone wants it to be named 2.22.0 instead of 2.21.1 please let me > > > > know. > > > > > > > > On Mon, Apr 25, 2022 at 11:42 AM Clebert Suconic > > > > wrote: > > > > > > > > > > I will call this release 2.21.1... > > > > > > > > > > > > > > > I only see improvements and bug fixes... I think for a 2.22.0 you > > > > > would need a new JIRA. > > > > > > > > > > > > > > > anyone strongly opinionated about calling it 2.22.0? > > > > > > > > > > On Fri, Apr 22, 2022 at 5:34 PM Clebert Suconic > > > > > wrote: > > > > > > > > > > > > cool... I will finish > > > > > > https://github.com/apache/activemq-artemis/pull/4012 and cut the > > > > > > release. Hoping monday.. but perhaps tuesday. > > > > > > > > > > > > On Fri, Apr 22, 2022 at 4:43 AM Robbie Gemmell < > > > > robbie.gemm...@gmail.com> wrote: > > > > > > > > > > > > > > Sounds like a great idea, I was also starting to think there > > > > > > > seemed > > > > > > > enough important things in there already, and releasing more often > > > > > > > would definitely be good either way. > > > > > > > > > > > > > > On Fri, 22 Apr 2022 at 03:28, Clebert Suconic < > > > > clebert.suco...@gmail.com> wrote: > > > > > > > > > > > > > > > > I will check the payload if that will be a 2.21.1 or a 2.22.0 > > > > > > > > (depending on new features or not), and make a release early > > > > > > > > next > > > > > > > > week. > > > > > > > > > > > > > > > > > > > > > > > > The branch is in nice shape and I would rather cut more > > > > > > > > often... we > > > > > > > > could make another one not long after. > > > > > > > > > > > > > > > > -- > > > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > -- > > > > > Clebert Suconic > > > > > > > > > > > > > > > > -- > > > > Clebert Suconic > > > > > > > > > > > > -- > Clebert Suconic -- Clebert Suconic
Re: [HEADS-UP] ActiveMQ Artemis 2.22.0 next week
yeah.. good point on the default behaviour.. On Wed, Apr 27, 2022 at 7:05 AM Robbie Gemmell wrote: > > Looking at what is currently in it, more improvements than bug fixes > and some changes in default behaviour, I would go with 2.22.0 > personally. > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARTEMIS%20AND%20fixVersion%20%3D%202.22.0%20ORDER%20BY%20issuetype%20DESC > > On Mon, 25 Apr 2022 at 21:44, Justin Bertram wrote: > > > > I'm fine with naming it 2.21.1. > > > > However, if you could hold the release until I fix ARTEMIS-3801 [1]. I hope > > to send a PR later today. > > > > > > Justin > > > > [1] https://issues.apache.org/jira/browse/ARTEMIS-3801 > > > > On Mon, Apr 25, 2022 at 10:53 AM Clebert Suconic > > wrote: > > > > > Of course I meant you would need a new feature for it to be 2.22.0... > > > I only see bug fixes and improvements... > > > > > > there was one JIRA that was recorded as feature: > > > > > > https://issues.apache.org/jira/browse/ARTEMIS-3765 > > > > > > > > > and I also consider it an improvement. > > > > > > > > > > > > > > > if anyone wants it to be named 2.22.0 instead of 2.21.1 please let me > > > know. > > > > > > On Mon, Apr 25, 2022 at 11:42 AM Clebert Suconic > > > wrote: > > > > > > > > I will call this release 2.21.1... > > > > > > > > > > > > I only see improvements and bug fixes... I think for a 2.22.0 you > > > > would need a new JIRA. > > > > > > > > > > > > anyone strongly opinionated about calling it 2.22.0? > > > > > > > > On Fri, Apr 22, 2022 at 5:34 PM Clebert Suconic > > > > wrote: > > > > > > > > > > cool... I will finish > > > > > https://github.com/apache/activemq-artemis/pull/4012 and cut the > > > > > release. Hoping monday.. but perhaps tuesday. > > > > > > > > > > On Fri, Apr 22, 2022 at 4:43 AM Robbie Gemmell < > > > robbie.gemm...@gmail.com> wrote: > > > > > > > > > > > > Sounds like a great idea, I was also starting to think there seemed > > > > > > enough important things in there already, and releasing more often > > > > > > would definitely be good either way. > > > > > > > > > > > > On Fri, 22 Apr 2022 at 03:28, Clebert Suconic < > > > clebert.suco...@gmail.com> wrote: > > > > > > > > > > > > > > I will check the payload if that will be a 2.21.1 or a 2.22.0 > > > > > > > (depending on new features or not), and make a release early next > > > > > > > week. > > > > > > > > > > > > > > > > > > > > > The branch is in nice shape and I would rather cut more often... > > > > > > > we > > > > > > > could make another one not long after. > > > > > > > > > > > > > > -- > > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > > -- > > > > > Clebert Suconic > > > > > > > > > > > > > > > > -- > > > > Clebert Suconic > > > > > > > > > > > > -- > > > Clebert Suconic > > > > > > -- Clebert Suconic
Re: nms-amqp repo default branch rename
Seems like this has now been done, via https://issues.apache.org/jira/browse/INFRA-23198, though Infra are awaiting feedback that everything went ok. On Mon, 4 Apr 2022 at 18:18, Timothy Bish wrote: > > On 4/4/22 13:12, Havret wrote: > > Sure, do you have the link to the previous ticket so I can clone it? > > > https://issues.apache.org/jira/browse/INFRA-21495 > > > Thanks, > > Havret > > > > On Mon, Apr 4, 2022 at 5:19 PM Robbie Gemmell > > wrote: > > > >> About a year ago we requested that Infra rename the default branches > >> to 'main' for the various git repositories. I have just noticed from > >> some push notification mails that the > >> https://github.com/apache/activemq-nms-amqp repository was missed out, > >> its branch was not renamed. > >> > >> I think we should raise another INFRA JIRA to get its default branch > >> renamed and align it with the others. Can one of the NMS maintainers > >> take care of this please, as infra will want verification that goes ok > >> etc? > >> > >> Robbie > >> > > -- > Tim Bish >
Re: [DISCUSS/NOTICE] NMS dist release area cleanup
As there has been no discussion toward not doing this (or indeed, at all), I will make this further cleanup next week if that continues to be the case. On Mon, 18 Apr 2022 at 16:35, Robbie Gemmell wrote: > > As noted in the previous mail, I had one other dist release area > cleanup suggestion that is slightly different than the others and so I > think needs discussion before any change. That being removing the > 1.5.x NMS releases in the following directory, specifically the 1.5.1 > NMS API release and the 1.5.4 NMS.Stomp client release: > https://dist.apache.org/repos/dist/release/activemq/apache-nms/1.5.0/ > > The API release is nearly 10 years old and was superceded multiple > times now, and it is heading for 9 years since the client release was > made, with current releases now being in the 1.8 or 2.0 streams. These > 1.5.x releases seem like they should be removed from the dist release > area and their site links updated to the archive, even despite it > being the latest for that particular client. There have been no > substantive commits made to the client repo for ~7 years and the > handful after that prior release have never been released. Given that, > personally I would also add a note on the release page that it isnt > being actively worked on anymore in addition to pointing the links to > the archive. > > Thoughts? > > On Mon, 18 Apr 2022 at 16:29, Robbie Gemmell wrote: > > > > There look to be various files (details below) in the NMS release area > > that should be cleaned up, being either superceded already or even > > apparently duplicate. I intend to remove the ones detailed below (and > > update the site links accordingly) in a couple of days unless > > discussion here suggests otherwise. > > > > I have another suggested NMS dist release area cleanup which I will > > reply to the thread with another mail for, as it as it is a little > > different than these and should be discussed first. > > > > > > The following 3 releases look like they should be removed, they arent > > marked as 'current' and so are only linked to from the archive on the > > site, only 2.0.0 ([1]) is linked to from the downloads site that these > > dirs populate: > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.0/ > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.1/ > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.2/ > > > > The following looks to be a duplicate copy of NMS.AMQP 2.0.0 that > > should be removed, with the parent dir actually being for the Openwire > > client instead, whereas the AMQP client is linked from the site via > > its expected apache-nms-amqp/2.0.0 dir [1]: > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-activemq/2.0.0/ > > > > The API release and Openwire client release in the following dir also > > seem like they can be removed and linked to the archive, as they have > > both been superceded by 1.8.0 [2][3] releases (or even 2.0.0) quite > > some time ago: > > https://dist.apache.org/repos/dist/release/activemq/apache-nms/1.7.0/ > > > > [1] > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/2.0.0 > > [2] > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-api/1.8.0/ > > [3] > > https://dist.apache.org/repos/dist/release/activemq/apache-nms-activemq/1.8.0/ > > > > Robbie
Re: [DISCUSS/NOTICE] NMS dist release area cleanup
After leaving it a week longer than I said, I have now made the below initial cleanups. On Mon, 18 Apr 2022 at 16:29, Robbie Gemmell wrote: > > There look to be various files (details below) in the NMS release area > that should be cleaned up, being either superceded already or even > apparently duplicate. I intend to remove the ones detailed below (and > update the site links accordingly) in a couple of days unless > discussion here suggests otherwise. > > I have another suggested NMS dist release area cleanup which I will > reply to the thread with another mail for, as it as it is a little > different than these and should be discussed first. > > > The following 3 releases look like they should be removed, they arent > marked as 'current' and so are only linked to from the archive on the > site, only 2.0.0 ([1]) is linked to from the downloads site that these > dirs populate: > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.0/ > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.1/ > https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/1.8.2/ > > The following looks to be a duplicate copy of NMS.AMQP 2.0.0 that > should be removed, with the parent dir actually being for the Openwire > client instead, whereas the AMQP client is linked from the site via > its expected apache-nms-amqp/2.0.0 dir [1]: > https://dist.apache.org/repos/dist/release/activemq/apache-nms-activemq/2.0.0/ > > The API release and Openwire client release in the following dir also > seem like they can be removed and linked to the archive, as they have > both been superceded by 1.8.0 [2][3] releases (or even 2.0.0) quite > some time ago: > https://dist.apache.org/repos/dist/release/activemq/apache-nms/1.7.0/ > > [1] https://dist.apache.org/repos/dist/release/activemq/apache-nms-amqp/2.0.0 > [2] https://dist.apache.org/repos/dist/release/activemq/apache-nms-api/1.8.0/ > [3] > https://dist.apache.org/repos/dist/release/activemq/apache-nms-activemq/1.8.0/ > > Robbie
Re: [HEADS-UP] ActiveMQ Artemis 2.22.0 next week
Looking at what is currently in it, more improvements than bug fixes and some changes in default behaviour, I would go with 2.22.0 personally. https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARTEMIS%20AND%20fixVersion%20%3D%202.22.0%20ORDER%20BY%20issuetype%20DESC On Mon, 25 Apr 2022 at 21:44, Justin Bertram wrote: > > I'm fine with naming it 2.21.1. > > However, if you could hold the release until I fix ARTEMIS-3801 [1]. I hope > to send a PR later today. > > > Justin > > [1] https://issues.apache.org/jira/browse/ARTEMIS-3801 > > On Mon, Apr 25, 2022 at 10:53 AM Clebert Suconic > wrote: > > > Of course I meant you would need a new feature for it to be 2.22.0... > > I only see bug fixes and improvements... > > > > there was one JIRA that was recorded as feature: > > > > https://issues.apache.org/jira/browse/ARTEMIS-3765 > > > > > > and I also consider it an improvement. > > > > > > > > > > if anyone wants it to be named 2.22.0 instead of 2.21.1 please let me know. > > > > On Mon, Apr 25, 2022 at 11:42 AM Clebert Suconic > > wrote: > > > > > > I will call this release 2.21.1... > > > > > > > > > I only see improvements and bug fixes... I think for a 2.22.0 you > > > would need a new JIRA. > > > > > > > > > anyone strongly opinionated about calling it 2.22.0? > > > > > > On Fri, Apr 22, 2022 at 5:34 PM Clebert Suconic > > > wrote: > > > > > > > > cool... I will finish > > > > https://github.com/apache/activemq-artemis/pull/4012 and cut the > > > > release. Hoping monday.. but perhaps tuesday. > > > > > > > > On Fri, Apr 22, 2022 at 4:43 AM Robbie Gemmell < > > robbie.gemm...@gmail.com> wrote: > > > > > > > > > > Sounds like a great idea, I was also starting to think there seemed > > > > > enough important things in there already, and releasing more often > > > > > would definitely be good either way. > > > > > > > > > > On Fri, 22 Apr 2022 at 03:28, Clebert Suconic < > > clebert.suco...@gmail.com> wrote: > > > > > > > > > > > > I will check the payload if that will be a 2.21.1 or a 2.22.0 > > > > > > (depending on new features or not), and make a release early next > > > > > > week. > > > > > > > > > > > > > > > > > > The branch is in nice shape and I would rather cut more often... we > > > > > > could make another one not long after. > > > > > > > > > > > > -- > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > -- > > > > Clebert Suconic > > > > > > > > > > > > -- > > > Clebert Suconic > > > > > > > > -- > > Clebert Suconic > > > >
