nickva commented on pull request #90: URL: https://github.com/apache/couchdb-pkg/pull/90#issuecomment-1033168514
> If you're saying, "pin each CouchDB version to a single Erlang major version for convenience packages", I do think that makes some sense. Even if we did adopt that policy (which I floated on dev@), one counter I have in this case is that CouchDB 3.2.1 is kinda/sorta not fully released yet from a packaging perspective, e.g. we never published any blog post on it or updated the homepage. I guess, or we'd decide release by release based on befits vs risk. I was thinking from the point of view of a user who updated to 3.2.1-0 and setup their repo to auto-upgrade then, they do to 3.2.1-1 but now their they might get slightly different performance characteristics or even breakage. However, in this case, like we saw there are already serious breakages so I after thinking more on it, we're probably fine updating. > I suspect our user community would be better off running newer releases instead of waiting for Cloudant to successfully upgrade its estate, but demonstrating that with any level of rigor is not a small project. I guess going by the point that we haven't actually officially announced 3.2.1 and only published the binary package (my fault for jumping the gun there), I see just going with 23 and updating. It strengthens the case for that at least. It looks like Cloudant is in the testing process and running benchmarks as we speak, we can always return back and make another package and pick another version or update some default vm.args flags or something. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
