Skip to content

Legacy or v2 for a new app? #345

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

Closed
Guuz opened this issue Apr 29, 2020 · 2 comments
Closed

Legacy or v2 for a new app? #345

Guuz opened this issue Apr 29, 2020 · 2 comments

Comments

@Guuz
Copy link

Guuz commented Apr 29, 2020

@krizzu Or anyone else that knows:

Should we use 1.9.0 or 2.0.0-rc.3 for a new project?

In #113 (comment) you mention you'll be less active for v2. Is v2 in general less active? Is it considered final? I see more development on the v1 than the v2 branch.

What is the recommendation for new projects to use?

@Guuz Guuz changed the title Legacy of v2 for a new app? Legacy or v2 for a new app? Apr 29, 2020
@krizzu
Copy link
Member

krizzu commented Apr 29, 2020

v1 (master) - the production version of Async Storage.
Consider v2 as a side try-project, which has not been tested throughly. Legacy backend is indeed v1 underneath.

Is v2 in general less active?

I'm open for discussions/PRs, it's just that when I can, I spend time on v1.

What is the recommendation for new projects to use?

v1 is more likely to have bug fixes quicker than on v2 now, so I'd say go with former.

@Guuz
Copy link
Author

Guuz commented Apr 30, 2020

Thanks for the quick response! Sounds like v1 is the better option for now. We'll go with that!

@Guuz Guuz closed this as completed Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants