-
Notifications
You must be signed in to change notification settings - Fork 287
Release 2.0.0 #152
Comments
Sounds good. Also, wishlist: |
Does it mean code in |
I've been using it in a production app for a few months. |
Should those exceptions be a new internal type, or is wording all that's needed? I think I've seen other code do a different type in this situation, but I can't recall where or why. |
Hello, I haven't seen any new activity here since June, and it's been almost 3 years since the last release i.e 1.2.3 - any idea when 2.0 will be released? |
No
…On Wed, Sep 13, 2017 at 5:46 PM Sandeep Raghuraman ***@***.***> wrote:
Hello, I haven't seen any new activity here since June, and it's been
almost 3 years since the last release i.e 1.2.3 - any idea when 2.0 will be
released?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#152 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEEETelxIiYyS6a5MnvhDjshst1hxW9ks5siE0mgaJpZM4MWJAC>
.
|
It's already very usable, so I encourage you to try it out
…On Wed, Sep 13, 2017 at 5:48 PM Jake Wharton ***@***.***> wrote:
No
On Wed, Sep 13, 2017 at 5:46 PM Sandeep Raghuraman <
***@***.***> wrote:
> Hello, I haven't seen any new activity here since June, and it's been
> almost 3 years since the last release i.e 1.2.3 - any idea when 2.0 will be
> released?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#152 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAEEETelxIiYyS6a5MnvhDjshst1hxW9ks5siE0mgaJpZM4MWJAC>
> .
>
|
Well I guess my concern is whether it's stable enough (in terms of bugs/crashes not API) to use for production apps. |
Yes. Master is stable and tested. This code powers production apps and sdks. |
Got it, thank you! |
For the remaining exceptions, Java 8's UncheckedIOException seems like a good choice in the future. A simple RuntimeException seems good for now. |
I think we're ready to release v2. I can cut 2.0.0-RC1, unless there are any objections? |
Yes, release it please. |
Please, release |
There is still no code to perform queue migration from v1 to v2 format. |
@JakeWharton do you think not having the the v1 -> v2 migration should be a blocker for 2.0.0-RC1? |
Yes, because it wouldn't be a candidate for release. Perhaps an alpha
instead.
…On Fri, Aug 31, 2018, 7:04 PM Prateek Srivastava ***@***.***> wrote:
@JakeWharton <https://github.com/JakeWharton> do you think that should be
a blocker for 2.0.0-RC1?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEEEcjTfcEmrpcoRFFqIKUNUAq6DN1kks5uWcDggaJpZM4MWJAC>
.
|
Makes sense. I'll rework #195 to be an alpha for now. |
Any idea when v2 will be released? |
Just wanted to make a list of what's left for 2.0.0.
Anything else?
The text was updated successfully, but these errors were encountered: