-1
A sunsetting discussion is very welcome, but this proposal is unclear,
based on week arguments and a lack of data, and as decision support
not the best of proposals.
1) To "table" a propoal for voting is problematic
--
OK:)
> On 6 Jul 2018, at 12:07, ermouth wrote:
>
>> Approximately how many 1.x nodes to you have in production now?
>> What is your estimated total no of users on these?
>
> Sorry, can’t disclose this kind of info publicly.
>
> All I can say I have zero nodes with 2.x in prod, despite we anal
> Approximately how many 1.x nodes to you have in production now?
> What is your estimated total no of users on these?
Sorry, can’t disclose this kind of info publicly.
All I can say I have zero nodes with 2.x in prod, despite we analyzed can
we migrate several times. We can’t, 2.x just does not
Thank you ermouth,
I am with your opinion.
I like CouchDB but I don't like how the devs behave currently.
It seems most of them do not really want to support the users and are
pushing only their own features with no respect to compatibility.
Sorry it is only how I observed the behavior back in tim
Thanks ermouth,
I agree with you that the logic behind the proposal could have been
clearer. A sunsetting announcement linked to the reliability criteria for 2.x
would have been preferable.
I value your opinions very much because I understand that you have
deployed large systems with CouchDB at t
