Github user rnewson commented on the issue:
https://github.com/apache/couchdb-fabric/pull/83
Fair. But even splitting into two commits would not be a signal to anyone.
If we want to support smooth hot upgrade between releases we have a lot more
work to do.
Sent from my iPhone
> On 12 Jan 2017, at 19:33, Paul J. Davis <[email protected]> wrote:
>
> I don't agree that upgrading a cluster without downtime is something only
Cloudant cares about. Granted we don't really have a process around this but I
think we'll want to figure something out for these sorts of issues.
>
> â
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
---
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.
---
