janl opened a new issue, #4396: URL: https://github.com/apache/couchdb/issues/4396
Via https://github.com/apache/couchdb/pull/4394#pullrequestreview-1263473784 It’d be nice if we tagged code that can be removed after we can expect everybody to have gone through a rolling cluster upgrade with the version number at which it can be removed, so we can semi-automate cleaning up said code. We could decide to make it a promise that if someone wants to do a rolling upgrade from N-1 to N, that if they are on the latest N-1 release that they can upgrade safely and that N no longer has the upgrade code. But all versions inside N-1 can be rolling-upgraded. That would reflect reality, especially outside IBM/Cloudant, where folks don’t track each and every CouchDB version. cc @mikerhodes -- 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]
