etcd-io
Rename the module to `go.etcd.io/bbolt/v2`
The main branch will be used as the development of bbolt v2
cc @fuweid @tjungblu @ivanvc @serathius
Why do we want to release 2.0? Are we planning any breaking changes? We should plan and think before we break users.
Why do we want to release 2.0?
Please read core-dependencies-mappings. It won't affect etcd release-3.[4-6]. bbolt 2.0 (the main branch) is targeting for future etcd version.
Are we planning any breaking changes?
Read
- https://github.com/etcd-io/bbolt/issues/789#issuecomment-2442071280
- https://github.com/etcd-io/bbolt/issues/472#issuecomment-1536207021
- a couple of other items which are still under discussion... to be finalized later
We should plan and think before we break users.
It doesn't necessary break users experience.
@ahrtr hello
Are there still work left for the cobra-migration ?
cc @ivanvc
Are there still work left for the cobra-migration ?
I think we can reuse the list from https://github.com/etcd-io/bbolt/issues/472#issuecomment-1674784719. But we may need to update it. I have a draft for bench.
