Do you accept PRs to align with bbolt, or stay BoltDB-only?

[asessa]

Hi,

since the original BoltDB is unmaintained; bbolt (go.etcd.io/bbolt) is the active fork.

Do you accept PRs that move the project toward bbolt (API, format, options, possibly a rename to bbolt-zig), or do you prefer to keep it strictly BoltDB-only?

[laohanlinux]

Only BoltDB, No free time to sync bbolt 😂

[asessa]

No problem at all, I completely understand that maintaining sync with bbolt takes time.
Since I need bbolt for a project and BoltDB is currently unmaintained, I'll proceed with my own fork implementing bbolt support. I'll rename it (e.g., bbolt-zig) to avoid any confusion with your repository and to keep the scopes distinct.
If anything from my work ends up being useful on your side, feel free to cherry-pick whatever you need. Likewise, if there's ever a lightweight way to contribute back without full bbolt sync, let me know.
Thanks for maintaining the project!