Skip to content

Conversation

@TomasHofman
Copy link
Contributor

@TomasHofman
Copy link
Contributor Author

TomasHofman commented Mar 11, 2021

Hello @belaban , would this change be all right?

Also, is there a 1.0.x branch somewhere? The issue was reported for EAP 7.3.x, which uses jgroups-kubernetes 1.0.13 currently. Or is it safe to upgrade to 2.0.x?

@belaban belaban merged commit cf79f55 into jgroups-extras:master Mar 11, 2021
@belaban
Copy link
Member

belaban commented Mar 11, 2021

Hi @TomasHofman
sure, applied.
Yes, there is a "1.x" branch, which uses the 4.x version of JGroups. You'd have to submit another PR against that branch if you want to release a jgroups-kubernetes 1.0.16. If you do that, I could release 1.0.16 right away...
Cheers,

@TomasHofman
Copy link
Contributor Author

@belaban Thanks.

I can't see the 1.x branch in this repo either. Only see master and stable.

@belaban
Copy link
Member

belaban commented Mar 11, 2021

Sorry, pushed now

@TomasHofman
Copy link
Contributor Author

Great, can see it now :). Downstream PR: #124

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants