[
https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945200&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945200
]
ASF GitHub Bot logged work on ARTEMIS-5174:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Nov/24 16:01
Start Date: 22/Nov/24 16:01
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #5366:
URL:
https://github.com/apache/activemq-artemis/pull/5366#issuecomment-2494099055
@AntonRoskvist, can you elaborate on what compatibility issues you saw when
upgrading?
Issue Time Tracking
-------------------
Worklog Id: (was: 945200)
Time Spent: 0.5h (was: 20m)
> Have dependabot ignore jgroups until JGRP-2794 is resolved
> ----------------------------------------------------------
>
> Key: ARTEMIS-5174
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5174
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Reporter: Anton Roskvist
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Before [JGRP-2794|https://issues.redhat.com/projects/JGRP/issues/JGRP-2794]
> is resolved, jgroups provides compatibility between versions on a
> "best-effort" basis. Since moving to upgrade jGroups through dependabot I
> have seen multiple cases where "rolling upgrades" between broker versions in
> a clustered setting does not work as intended.
> I therefore think dependency updates to jgroups should be made manually on a
> case by case basis until the aforementioned jgroups Jira ticket is resolved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
