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.

Sign up for GitHub

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

Jump to bottom

Tracking issue of RFC Config Backward Compatibility #5297

Closed
6 tasks done
Xuanwo opened this issue May 11, 2022 · 1 comment
Closed
6 tasks done

Tracking issue of RFC Config Backward Compatibility #5297

Xuanwo opened this issue May 11, 2022 · 1 comment

Comments

@Xuanwo
Copy link
Member

Xuanwo commented May 11, 2022 •
edited
Loading

Background

There should be a ver to identify the proto-conv version if this message has chances to be used alone. Otherwise, without a ver, it implies proto-conv will always have to be able to deal with any old version S3StorageConfig message.

Originally posted by @drmingdrmer in #5280 (comment)

RFC

Config Backward Compatibility

Roadmap

Unresolved Problems

  • serde alias may not work as expected, we need to handle the backward compatibility by hand
@Xuanwo Xuanwo mentioned this issue May 11, 2022
Merged
@Xuanwo Xuanwo changed the title feat: Config Compatibility Design Tracking issue of RFC Versioned Config May 12, 2022
@Xuanwo Xuanwo changed the title Tracking issue of RFC Versioned Config Tracking issue of RFC Config Backward Compatibility May 13, 2022
This was referenced May 16, 2022
Merged
Closed
Merged
Merged
@Xuanwo Xuanwo moved this to 📋 Backlog in Xuanwo's Work Sep 15, 2022
@Xuanwo
Copy link
Member Author

Xuanwo commented Sep 15, 2022

Most work have been done. Let's close.

@Xuanwo Xuanwo closed this as completed Sep 15, 2022
@Xuanwo Xuanwo moved this from 📋 Backlog to 📦 Done in Xuanwo's Work Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Xuanwo