-
Notifications
You must be signed in to change notification settings - Fork 646
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
refactor: merge bolt and guts_cli #394
Conversation
I support the direction. Thank you for this refactoring. The plan I was thinking about assumed:
v1.3.5 is already 2.5 year old. |
Actually v1.3.6 was released Jun 2, 2021. I agree to release 1.3.7 firstly. Let me trigger a pipeline to verify bolt in etcd's pipeline, if there is no any issue, then we can tag v1.3.7 |
Indeed it was tagged (and used in etcd) but not publised on: https://github.com/etcd-io/bbolt/releases |
v1.3.7 is already released, this PR will only target v1.4.0. |
@ptabor could you please take a look this PR? I am planning to fix the following two issues on top of this PR, |
Points: 1. There are lots of duplicated definitions between bolt and guts_cli, which is definitely not good. 2. The implementation in guts_cli also has issue, please refer to #391. This refactoring can fix the issue. Signed-off-by: Benjamin Wang <wachao@vmware.com>
Signed-off-by: Benjamin Wang <wachao@vmware.com>
Closing this PR, and let me continue to work on #407 |
Points:
Moved all common definitions into package
internal/common
. Majority other changes are basically mechanical changes.Signed-off-by: Benjamin Wang wachao@vmware.com