-
-
Notifications
You must be signed in to change notification settings - Fork 588
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
🚀 Feedback for drafts of v4.2.2 #385
Labels
release
Discuss a new release.
Comments
jsamr
changed the title
Feedbacks for drafts of v4.2.2
🚀 Feedbacks for drafts of v4.2.2
Jul 21, 2020
jsamr
changed the title
🚀 Feedbacks for drafts of v4.2.2
🚀 Feedback for drafts of v4.2.2
Jul 21, 2020
This was referenced Jul 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear community,
You might have noticed this (awesome) project hasn't been maintained for a while, and a lot of issues an PRs have piled up. After noticing a few contributions I had made, @Exilz offered me to join the team, and I accepted with great enthusiasm! I am really glad to participate in reviving this project, bring-in great new features and help build a community of collaboration. But before that, a certain amount of work has to be done to address pending issues.
After two weeks of sustained work, a draft of release v4.2.2 is ready to be tested! This release offers a lot of fixes, they are all listed in the changelog. Despite the fact that many tests have been implemented to limit the risks of introducing new bugs, these precautions cannot replace manual tests on physical devices (we don't have a Detox setup, yet). So to play it safe, we're relying on your help! We will also try to adopt this practice as a workflow in the future.
To test this release, simply install the package with the next tag:
Please tell us how it works out for you! Don't forget to mention the exact version you're testing. Current latest
next
tag:And build status:
You're also welcome to ask anything related to this release, and pinpoint code-changes you wish to comment. This ticket will stay open for a while, until a sufficient amount of feedback is collected. In the meantime, the work for the next major will continue. You can watch the advancement here.
The text was updated successfully, but these errors were encountered: