+1

built from source and ran through the test suite

On Fri, Apr 29, 2022 at 2:14 AM Francesco Nigro <nigro....@gmail.com> wrote:

> +1 binding
> Very happy re the change on the cluster connection!!!
>
> Il gio 28 apr 2022, 18:25 Clebert Suconic <clebert.suco...@gmail.com> ha
> scritto:
>
> > I would like to propose an Apache ActiveMQ Artemis 2.22.0 release.
> >
> >
> > There are no new features on this release, however there are many
> > improvements and bug fixes.
> >
> > In particular there's a default change on cluster connections where we
> > now use 1MB bytes for flow control, avoiding Out Of Memory exception
> > on situations with high latency networking:
> >
> > * ARTEMIS-3083 Set a default producer-window-size on cluster connection
> >
> >
> > There are many other improvements and bug fixes and the full release
> > notes is available here for more information:
> >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12351488
> >
> >
> > Ths git commit report is here:
> >
> >
> https://activemq.apache.org/components/artemis/download/commit-report-2.22.0
> >
> >
> > Source and binary distributions can be found here:
> > https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.22.0
> >
> > The Maven staged repository is here:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1251
> >
> >
> > In case you want to give it a try with the maven repo on examples:
> >
> >
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
> >
> >
> > The source tag:
> >
> >
> >
> https://gitbox.apache.org/repos/asf/activemq-artemis.git;a=tag;h=refs/tags/2.22.0
> >
> >
> > [ ] +1 approve this release
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> >
> > Here's my +1 (Binding) vote
> >
> >
> >
> > I should keep this release open for 72 Hours, and I'm not going to
> > count the weekend as business hours. That means I will keep this
> > release open until at least May-3rd, Noon USA EST.
> >
>

Reply via email to