-
Notifications
You must be signed in to change notification settings - Fork 547
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 package to org.roaringbitmap.v1 or org.roaringbitmap.v2 #463
Milestone
Comments
I consider current package as some sort of v1.
We may argue current package is rathrr some sort of v0, like mvn 0.X
Then, moving package to v1, and mvn to 1.x looks hood to me.
Le jeu. 11 févr. 2021 à 20:05, Daniel Lemire <[email protected]> a
écrit :
… We are about to merge this API breaking changes to
https://github.com/RoaringBitmap/RoaringBitmap/tree/1.0-SNAPSHOT
It has been proposed in #461
<#461> that we rename
the package.
I do not mind jumping directly to v2, but consider that we never reached
v1... and I am not exactly sure why would skip v1.
cc @blacelle <https://github.com/blacelle> @richardstartin
<https://github.com/richardstartin>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#463>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQFCFZ3EM5K74QB3FFX6ALS6QS6LANCNFSM4XPL7EGQ>
.
|
I’d just called it org.roaringbitmap.v1 and align it with the library version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are about to merge this API breaking changes to
https://github.com/RoaringBitmap/RoaringBitmap/tree/1.0-SNAPSHOT
It has been proposed in #461 that we rename the package.
I do not mind jumping directly to v2, but consider that we never reached v1... and I am not exactly sure why would skip v1.
cc @blacelle @richardstartin
The text was updated successfully, but these errors were encountered: