[DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Robbie Gemmell <ro...@gmail.com>]

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 May.

Java 11 has been the current Java LTS release since September 2018,
and Java 17 will arrive in September to supplant even it. It is over 4
years since we required Java 8+ usage, which was itself a bit over 2
years after first requiring Java 7+ usage (in the old JMS client, the
current one started out on Java 7+). I have seen other projects
discussing transition to Java 11+ for over a year now, with some since
having made the change and some being in progress or imminently so. I
think now is an appropriate time to begin requiring Java 11+.

On the version number I think the codebase has been stable for several
years and the API is fixed, so it's probably long overdue that we just
did it. Other versions numbers are still available if we need them
later.

Doing both at the same time would make it simpler/clearer to
distinguish old and new, simplifying doing future maintenance releases
for the old 0.x line to support JDK8 users for a further period of
time, for example if a security issue arises or just to backport some
important fixes.

Thoughts?

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Robbie Gemmell <ro...@gmail.com>]

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 that requires 11+,
not that we won't do further 0.x releases supporting Java 8+. The
existing releases will work just as well on Java 8 as they do now, and
if something especially serious comes up we can look to backport it (I
expect I'd be happy doing one every so often for bug fixes for at
least the next year). No matter how much notice is given there are
always folks who just continue using the old version (or more
realistically, an ever older-still stale version of it :P).

(Also, this discussion is only about qpid-jms-client, not
qpid-broker-j; I'll leave any planning on that front to Alex given he
is the one actually maintaining its releases)

On Thu, 15 Apr 2021 at 15:55, Tom Jordahl <tj...@adobe.com.invalid> wrote:
>
> 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 months of back porting of the (expected) very few bugs to the 0.x branch
> - Announce end-of-bug fixing for 0.x as of October 1, 2021
>
> What do you think?
> --
> Tom
>
> From: Robbie Gemmell <ro...@gmail.com>
> Reply-To: "users@qpid.apache.org" <us...@qpid.apache.org>
> Date: Thursday, April 15, 2021 at 8:16 AM
> To: users <us...@qpid.apache.org>
> Subject: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+
>
> 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 May.
>
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
>
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
>
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
>
> Thoughts?
>
> Robbie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org<ma...@qpid.apache.org>
> For additional commands, e-mail: users-help@qpid.apache.org<ma...@qpid.apache.org>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Tom Jordahl <tj...@adobe.com.INVALID>]

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 months of back porting of the (expected) very few bugs to the 0.x branch
- Announce end-of-bug fixing for 0.x as of October 1, 2021

What do you think?
--
Tom

From: Robbie Gemmell <ro...@gmail.com>
Reply-To: "users@qpid.apache.org" <us...@qpid.apache.org>
Date: Thursday, April 15, 2021 at 8:16 AM
To: users <us...@qpid.apache.org>
Subject: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

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 May.

Java 11 has been the current Java LTS release since September 2018,
and Java 17 will arrive in September to supplant even it. It is over 4
years since we required Java 8+ usage, which was itself a bit over 2
years after first requiring Java 7+ usage (in the old JMS client, the
current one started out on Java 7+). I have seen other projects
discussing transition to Java 11+ for over a year now, with some since
having made the change and some being in progress or imminently so. I
think now is an appropriate time to begin requiring Java 11+.

On the version number I think the codebase has been stable for several
years and the API is fixed, so it's probably long overdue that we just
did it. Other versions numbers are still available if we need them
later.

Doing both at the same time would make it simpler/clearer to
distinguish old and new, simplifying doing future maintenance releases
for the old 0.x line to support JDK8 users for a further period of
time, for example if a security issue arises or just to backport some
important fixes.

Thoughts?

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org<ma...@qpid.apache.org>
For additional commands, e-mail: users-help@qpid.apache.org<ma...@qpid.apache.org>

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Timothy Bish <ta...@gmail.com>]

+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 otherwise I would look to release such a
> combination in May.
>
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
>
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
>
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
>
> Thoughts?
>
> Robbie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
> .


-- 
Tim Bish


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Oleksandr Rudyy <or...@gmail.com>]

+1 to both: JDK11 and bumping Qpid JMS up to version 1.0.0

On Thu, 15 Apr 2021 at 13:16, Robbie Gemmell <ro...@gmail.com> 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 otherwise I would look to release such a
> combination in May.
>
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
>
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
>
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
>
> Thoughts?
>
> Robbie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Gary Tully <ga...@gmail.com>]

that makes sense to me. 1.0 is long over due

On Thu, 15 Apr 2021 at 13:16, Robbie Gemmell <ro...@gmail.com> 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 otherwise I would look to release such a
> combination in May.
>
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
>
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
>
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
>
> Thoughts?
>
> Robbie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Steve Huston <sh...@riverace.com>]

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 <ro...@gmail.com> 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 otherwise I would look to release such a
> combination in May.
> 
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
> 
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
> 
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
> 
> Thoughts?
> 
> Robbie
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org