-
Notifications
You must be signed in to change notification settings - Fork 43
Compatibility guarantees for updating Tarantool #2218
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
Labels
release-notes
Writing and editing release notes
server
[area] Task relates to Tarantool's server (core) functionality
Comments
JFYI: there's also an issue about describing iterator compatibility guarantees #2102 |
xuniq
added a commit
that referenced
this issue
Apr 5, 2022
Fixes #2218 Based on the RFC (tarantool/tarantool#6182) by Alexander Turenko. Proofread by Kseniia Antonova, reviewed by Alexander Turenko and Patience Daur. Co-authored-by: Patience Daur <[email protected]>
Not exactly: the linked issue is about so called stability guarantees. IOW, it is how the iterator behaves in case of database modifications during traversal using the iterator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
release-notes
Writing and editing release notes
server
[area] Task relates to Tarantool's server (core) functionality
Epic: Release notes
Related issues:
Clarify tarantool update process to a newer major version (#836)
Guide to upgrade from 1.6 to 1.10 (tarantool/#4934)
Compatibility guarantees
Write about compatibility guarantees for updating to the new Tarantool version
Product: Tarantool
Since: 2.x
Audience/target: admins, developers, CTO's who decide if they can update Tarantool to 3.x or not
Root document: TBA, somewhere around release notes?
SME: @Totktonada @kyukhin
Peer reviewer: @NickVolynkin
The text was updated successfully, but these errors were encountered: