Let's analyze the current community release testing strategy and decide whether, based on both product and technical requirements, it warrants improvement. If so, how can we assist the community in doing so? And, in particular, what can we do to:
Help guarantee that every feature in each release is as well-tested as possible, in such a way to minimize the introduction of last-minute bugs;
Help the Product Working Group communicate with whoever is doing the testing, so that the latter effort can be factored into the plan for upcoming releases.
And finally:
How much of the testing should be delegated to the development teams? To the reviewers? To a dedicated testing team?
Part I. Overview of the current community testing strategy
Links to existing documentation:
Announcement: https://discuss.openedx.org/t/join-the-test-team-for-quince-and-meet-the-test-champions-from-palm/11503
Test Sheet: https://docs.google.com/spreadsheets/d/1oVhrnRjk7zxUHMNyU8bJ-TLKyaSukLmN3jWom17O7pI/edit#gid=0
Project Board: https://github.com/orgs/openedx/projects/28/views/5
Example release blocker: https://github.com/openedx/wg-build-test-release/issues/318
Part II. What should probably continue?
List the things that have worked well so far, and likely shouldn’t be messed with.
Part III. What should probably change?
Things that haven’t worked very well at achieving stated objectives, aren’t current done (but probably should), etc. Anything to add ,remove, or modify.
Part IV. The weeds: how, exactly?
How can we help implement the changes? Are there specific patterns or tools to recommend? Who should lead this - should it continue to be delegated to BTR? What are the next steps?