1fbcbb73a0
This is waiting on - https://github.com/flutter/flutter/pull/148777 - https://github.com/flutter/flutter/pull/148790 After this PR lands, there will likely be 1-2 more clean up PRs, after which the migration will be done! --- This moves the remaining wiki pages as planned in [flutter.dev/go/migrate-flutter-wiki-spreadsheet](https://docs.google.com/spreadsheets/d/1x65189ZBdNiLRygpUYoU08pwvXD4M-Z157c6pm8deGI/edit?usp=sharing) It also adds the team labels to the label bot for future PRs. Changes to the content were only updating cross links, or links to refer to the main branch rather than master. Remaining links to the wiki will be updated once all other pages have finished moving, they still work in the meantime. Part of https://github.com/flutter/flutter/issues/145009
1.1 KiB
With each beta we need to test that there are no regressions. We have lots of automated tests, but sometimes the thing that breaks is something we hadn't thought to test (or haven't figured out how to test) and so human testing is important!
When to test betas
We announce betas on our Discord (see the Chat page for the invite link), in the #releases channel, about once a month.
How to get a beta build
When a beta build is announced, switch to the beta channel:
flutter channel beta && flutter upgrade
If you get a git error, then you probably have a contributor checkout of Flutter. Use git instead:
git fetch upstream/beta && git checkout beta
Either way, check that everything is as you expect:
flutter --version
It should specify the version number that you are testing.
How to test a beta build
This is the easiest part: just use it! Test it on your projects, try running demos, try doing things you depend on normally.
Tell others who are testing the beta branch what you're doing in #quality-assurance on Discord!
In time, we will collect some specific things to try out here.