>
> +1 on moving forward without JMS 2.0 until 5.18.0.
+1.
Just one question, since 5.17.0 is reported as a release with major updates
[1], I haven't found so far [2] if a migration guide will need to
be created for this release?
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pa
Also, obviously I meant 5.17, 5.18, etc as this is not Artemis :)
On Tue, Feb 22, 2022 at 3:10 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> In terms of maintenance if we get out 2.18, 2.19, etc then 2.17 can just
> get important fixes or be made EOL and we can move on. Long
In terms of maintenance if we get out 2.18, 2.19, etc then 2.17 can just
get important fixes or be made EOL and we can move on. Long lived branches
and support are not necessary if we keep up with more frequent releases.
2.17.0 is at a logical cut off point where it's at now and I'm definitely
not
Hey All-
I get the idea that getting a JDK 11-based released is a good thing, but I also
think we should consider the jakarta alignment as part of what active branches
are supported. This is the path other projects have taken and helps users align
things when they are assembling pieces for thei
+1 from me, the JMS 2.0 stuff can bake a bit longer and be in the next
release
On 2/22/22 09:23, Robbie Gemmell wrote:
It is very much OK with me.
(You'll most often see me moaning about not releasing enough, and
putting too much in single releases, rather than the reverse).
On Tue, 22 Feb 20
It is very much OK with me.
(You'll most often see me moaning about not releasing enough, and
putting too much in single releases, rather than the reverse).
On Tue, 22 Feb 2022 at 14:17, Jean-Baptiste Onofré wrote:
>
> I agree.
>
> @Matt @Robbie @Tim is it ok for you to have 5.17.0 with Spring5,
I agree.
@Matt @Robbie @Tim is it ok for you to have 5.17.0 with Spring5,
log4j2, JDK11 and include JMS2 in 5.18.0 that can happen quickly ?
Regards
JB
On Tue, Feb 22, 2022 at 3:09 PM Christopher Shannon
wrote:
>
> I'm +1 on moving forward without JMS 2.0 until 5.18.0. The reality is there
>
I'm +1 on moving forward without JMS 2.0 until 5.18.0. The reality is
there is no consensus to keep it in 5.17.0. There are multiple people who
do not want to include it in 5.17.0 so it's time to move on without. We
also need to revert the commits from
https://issues.apache.org/jira/browse/AMQ-730
Hi guys,
Quick update about 5.17.0 release:
- I fixed/squash log4j2 update PR
(https://github.com/apache/activemq/pull/662). I think it's OK (I'm
waiting for the end of Jenkins).
- I'm creating Apache POM 25 update PR
- I'm creating Spring 5.3.16 update PR
So, ActiveMQ 5.17.0 is almost ready fro
