On Tue, 4 Mar 2025 10:38:08 -0500, Christopher Shannon
<christopher.l.shan...@gmail.com> wrote:

| I've actually been wondering if we should just bump the major version to
| 4.0.0, but at the very least with all the work here certainly 3.10.0
| 
| One other thing to note is the OpenWire version is probably out of date
| (OpenWire is up to 12 and eventually will go to 13 if we add shared
| subscription support and other changes). At some point this could be
| brought up to date although the generator that was being used in the
| ActiveMQ project no longer works on newer versions so that would need to be
| figured out.

I think the version bump to 4.0.0 should wait until the Openwire
update.  That could potentially be a major change, justifying the
change in the major version number.

Right now, the API hasn't been impacted at all - the changes have been
internal, just beefing up the code base.

A quick note, that the 3.10.x branch already exists, forked off
release 3.9.4 a while back, with at least one important fix. I'm not
sure if that fix was replicated in 3.9.5. At any rate some intelligent
merging will be needed.

Right now, my PR is for a merge into 3.9.x.  Say we tag the result
3.9.6.  On 3.10.x, we can tag the current state at 3.10.0, then
merge/rebase 3.9.6 on top of that and tag it 3.10.1, for releaae.  Or
is that too involved?

Arjun       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org
For additional commands, e-mail: dev-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact


Reply via email to