-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add shift operations to BitSet #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Can you squash your commits?
e306912
to
ad3e1c4
Compare
Sure, squashed them. |
Thanks! |
@julienrf, I realized that the documentation links which I added to README for BitSet shifts are incorrect (and probably could not be implemented until the next release), sorry for that. |
Ah, indeed we will have to update these links at the next release. We should probably do another release soon anyway because we have added a bunch of cool things (BitSet shift operations, @SethTisue How do we decide when we should release a 1.0.0 version? |
um, I don't really have an opinion about that. @szeiger opinion? |
ping @szeiger |
Let's look into this after 2.13.1. |
I’ve just published a 0.2.0 version, can someone with the appropriate rights release it from the staging repository on Sonatype? |
I see two open staging repos with 0.2.0. Both appear to have the same JVM artifacts. One additionally has sjsj 1.0.0-M8 artifacts, the other one has sjs 0.6 artifacts. |
Ah, I believe one has been build on jdk11 and the other one on jdk8. We need to tweak the script. |
Is one of them good for a release or should I delete both? |
Unfortunately none of them is complete, you should delete both. Thanks! |
I just noticed that there are even two repositories with the JVM + ScalaJS 0.6 artifacts. I suppose this is from JDK 8 and 11 and the one with ScalaJS 1.0.0-M8 is yet another build. |
Everything dropped. |
We previously run the CI tasks on the root module, which aggregates both the JS and JVM modules. This resulted in wasting CPU and duplicating releases on Sonatype (see #43 (comment))
We previously run the CI tasks on the root module, which aggregates both the JS and JVM modules. This resulted in wasting CPU and duplicating releases on Sonatype (see #43 (comment))
We previously run the CI tasks on the root module, which aggregates both the JS and JVM modules. This resulted in wasting CPU and duplicating releases on Sonatype (see #43 (comment))
A
BitSetDecorator
that adds<<
and>>
operations (bitwise shift) toBitSet
collections.Solves #41