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

Rename the module to go.etcd.io/bbolt/v2 #897

Open
ahrtr opened this issue Feb 7, 2025 · 4 comments
Open

Rename the module to go.etcd.io/bbolt/v2 #897

ahrtr opened this issue Feb 7, 2025 · 4 comments
Assignees

Comments

@ahrtr
Copy link
Member

ahrtr commented Feb 7, 2025

The main branch will be used as the development of bbolt v2

cc @fuweid @tjungblu @ivanvc @serathius

@ahrtr ahrtr self-assigned this Feb 7, 2025
@serathius
Copy link
Member

serathius commented Feb 7, 2025

Why do we want to release 2.0? Are we planning any breaking changes? We should plan and think before we break users.

@ahrtr
Copy link
Member Author

ahrtr commented Feb 7, 2025

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

We should plan and think before we break users.

It doesn't necessary break users experience.

@Elbehery
Copy link
Member

Elbehery commented Feb 9, 2025

@ahrtr hello

Are there still work left for the cobra-migration ?

cc @ivanvc

@ivanvc
Copy link
Member

ivanvc commented Feb 9, 2025

Are there still work left for the cobra-migration ?

I think we can reuse the list from #472 (comment). But we may need to update it. I have a draft for bench.

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

No branches or pull requests

4 participants