I dont see a great need or benefit to delay doing a 1.0.0 release or
introducing a Java 11+ stream over a significant period at this point,
no. This time last year, perhaps...but now, I think it is a suitable
time to simply get the ball rolling.
Note I'm only saying to do a 1.0.0 client release
+1
On 4/15/21 8:15 AM, Robbie Gemmell wrote:
Hi folks,
I would like to propose bumping Qpid JMS up to version 1.0.0+ for
future releases, and simultaneously require Java 11+ for those new
releases, leaving further Java 8 support efforts with the existing 0.x
stream. Barring discussion
We are using Qpid and the JMS client library on Java 8. We have plans to move
to 11 before the end of the year.
Maybe we could do this over a longer time period?
Something like:
- 3 month warning for the release of 1.0 which drops support for Java < 11
- Release 1.0 ~July 1, 2021
- Continue 2
I agree, Robbie. Good idea.
Steve Huston
(sent from my iPhone - please excuse brevity and typos)
> On Apr 15, 2021, at 8:16 AM, Robbie Gemmell wrote:
>
> Hi folks,
>
> I would like to propose bumping Qpid JMS up to version 1.0.0+ for
> future releases, and simultaneously require Java 11+
that makes sense to me. 1.0 is long over due
On Thu, 15 Apr 2021 at 13:16, Robbie Gemmell wrote:
>
> Hi folks,
>
> I would like to propose bumping Qpid JMS up to version 1.0.0+ for
> future releases, and simultaneously require Java 11+ for those new
> releases, leaving further Java 8 support
Hi folks,
I would like to propose bumping Qpid JMS up to version 1.0.0+ for
future releases, and simultaneously require Java 11+ for those new
releases, leaving further Java 8 support efforts with the existing 0.x
stream. Barring discussion otherwise I would look to release such a
combination in
