New Builds Team
The New Builds Test Team is a proposed initiative to widen our pool of testers between releases.
- This is mostly for selected builds, ones that could be suitable for production use.
- A small number of people from the new builds team will go on to test alphas too.
Have 'Calls for testing' in which we invite testing of new features. Possible examples:
- Timer Record
- Dark Theme
- MIDI out enabled.
These might not be actual release candidates, they could be branches that are being worked on. These calls will be for Audacity versions we already have significant confidence in. Crash and burn bugs (when not using the new features) should be very rare indeed.
Testers will sign up in advance, and will get alphas to test when development is ready - not a fixed schedule. If several compatible changes are available at the same time, we should merge them into one test build, so that there is more for testers to try out in each build.
James thinks we will have most success with builds that have multiple new features in them, curated by one person, 'auteur builds'.
One option is to use Audacity Facebook page for these build announcements, including at least a screenshot of the new feature.
- When we learn of a serious problems with a build, we need to post a comment about the issue. That way users actually using the builds in production can do so with much greater safety than otherwise.
Peter 16Feb17: We could also use the Wikipedia page on Audacity. In the info pane on the right of the page there is an entry for "Preview Release" for which our current entry states "None". We could use this field to drive users to a recruitment page for Tester recruiting and give them access to these test builds and Release Candidates for download.
Peter 24Feb17: I suggest we add a page on the Audacity Website to invite testers on board. This could be linked to from the "Get Involved" tab, where we would add a new sub-menu entry for "Testers". We could maybe also add a link to that page from the Download pages.