Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comments to mixed-cluster upgrade code #4396

Open
janl opened this issue Jan 20, 2023 · 0 comments
Open

Add comments to mixed-cluster upgrade code #4396

janl opened this issue Jan 20, 2023 · 0 comments

Comments

@janl
Copy link
Member

janl commented Jan 20, 2023

Via #4394 (review)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants