Github user cammckenzie commented on the issue:
https://github.com/apache/curator/pull/208
I think that this is OK.
I'm just wondering what the best way forward is after this release? Ideally
we don't want to have to have users opt in to pick up CURATOR-275 do we? I've
never used the service discovery stuff, so I'm not sure if that's an issue.
Should the next release after the one that includes this have the
serialization of enabled set to true? Then we would have an upgrade path from
pre 2.12.x to 2.12.x+1 (with this fix) to 2.12.x + 2?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
