-
Notifications
You must be signed in to change notification settings - Fork 37
Upcoming release? #75
Comments
I also can't upgrade wartremover to 0.14 to due to binary compat since M4/20150427 both use 0.10, and I noticed it's been removed in master. |
I’d love to issue a new release, but I have not extensively used the code introduced by the newer commits, and currently I’m not developing anything on Android, which means I don’t have the opportunity to do so. Guys from @47deg kindly agreed to carry the torch, but it might take a while until everything is settled. So I guess there will be a new release, but not sure when :) |
I could pitch in if help is needed. |
@joprice we can use some help if you'd like to contribute preparing the next release. |
Sounds good. Feel free to email me to catch me up on the current status and what needs to be done. |
Talked to @javipacheco and he will contact you and @stanch with a list of things where we need help in order to prepare the next release. |
I'm using
v2.0.0-20150427
even though the docs sayv2.0.0-M4
is the latest. I found it haphazardly by starting from some example code that was usingContextWrapper
instead ofAppContext/ActivityContext
. Even though this is newer, sbt-updates always tells me to upgrade to M4. It can be a bit confusing and probably causes some adopters to stumble. Is there going to be another milestone with this change, or a v2 release?The text was updated successfully, but these errors were encountered: