Skip to content
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.

Release 2.0.0 #152

Open
2 tasks done
f2prateek opened this issue Mar 7, 2017 · 19 comments
Open
2 tasks done

Release 2.0.0 #152

f2prateek opened this issue Mar 7, 2017 · 19 comments

Comments

@f2prateek
Copy link
Collaborator

f2prateek commented Mar 7, 2017

Just wanted to make a list of what's left for 2.0.0.

Anything else?

@NightlyNexus
Copy link
Contributor

Sounds good.

Also, wishlist:
Samples can always come in later.
If Converter artifacts end up being something people want, they could be introduced in a point release.

@darktiny
Copy link

Does it mean code in master branch is ready for production usage ?

@f2prateek
Copy link
Collaborator Author

I've been using it in a production app for a few months.
Generally the code on master is always ready to be used for production. Only the APIs aren't guaranteed to be stable (i.e. they could be changed/removed).

@NightlyNexus
Copy link
Contributor

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.

@sandeep-voxer
Copy link

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?

@JakeWharton
Copy link
Collaborator

JakeWharton commented Sep 13, 2017 via email

@JakeWharton
Copy link
Collaborator

JakeWharton commented Sep 13, 2017 via email

@sandeep-voxer
Copy link

Well I guess my concern is whether it's stable enough (in terms of bugs/crashes not API) to use for production apps.

@NightlyNexus
Copy link
Contributor

Yes. Master is stable and tested. This code powers production apps and sdks.
The API is not stable but probably won't change much if at all.

@sandeep-voxer
Copy link

Got it, thank you!

@NightlyNexus
Copy link
Contributor

For the remaining exceptions, Java 8's UncheckedIOException seems like a good choice in the future. A simple RuntimeException seems good for now.

@f2prateek
Copy link
Collaborator Author

I think we're ready to release v2. I can cut 2.0.0-RC1, unless there are any objections?

@goghAta
Copy link

goghAta commented Aug 22, 2018

Yes, release it please.

@dimhold
Copy link

dimhold commented Aug 22, 2018

Please, release

@JakeWharton
Copy link
Collaborator

There is still no code to perform queue migration from v1 to v2 format.

@f2prateek
Copy link
Collaborator Author

f2prateek commented Aug 31, 2018

@JakeWharton do you think not having the the v1 -> v2 migration should be a blocker for 2.0.0-RC1?

@JakeWharton
Copy link
Collaborator

JakeWharton commented Aug 31, 2018 via email

@f2prateek
Copy link
Collaborator Author

Makes sense. I'll rework #195 to be an alpha for now.

@sjoerd-michels
Copy link

Any idea when v2 will be released?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants