...
VI. Action Items for Sumac release 📈
Product
[Jenna]: Creating a Gantt chart to track every major project/feature for the next release at a more granular level (epics) instead of at a high level (project) to better assess the risk of whether delivering or not each one of the new features and plan the testing process and required capacity better and in advance.
[Jenna]: Make the Release planning meeting a monthly one and include it in the Community calendar to make sure we start planning every release with enough anticipation.
[Jenna]: Product to update https://docs.google.com/spreadsheets/d/1tWgp9LXNg4sfWYd_0ghNl6qfIZZ9851MtGBXPeSgzFs/edit?gid=0#gid=0 with current plans for Sumac, ahead of the August monthly planning
[Jenna] To discuss: A new role for a product-BTR liaison/coordinator
To coordinate bug prioritization
To collaborate with testing manager to write and manage regression and AC tests
Testing
[Adolfo]: Continue the conversation about community-supported and always-available sandbox environments.
[Sarina & Adolfo]: Asking the Maintenance WG about the branch cutting and release date.
[Peter]: Review all the tests.
Remove ones that are no longer relevant.
Write better test descriptions for legacy tests, in the style of the new Redwood tests.
Look for opportunities to automate tests.
[Peter]: To discuss: should we invest in the test course repo?
[Maria]: review issues reported on the board with “no test id” or “no test case” to decide whether to include them in the test sheet or specify which test they are part of
Bug triage and fixing
[Maria]: Try to solve issues on the board alongside maintainers to avoid accumulating them for Sumac
[JennaJorge] To discuss: A new role for a product-BTR liaison/coordinator
To coordinate bug prioritization
To collaborate with testing manager to write and manage regression and AC tests
[Jenna]: Adding the Product Liaison role to the process: Document the communication process, calls for help, and working agreements between the BTR WG and the Maintainers WG to get them more involved and engaged in the Open edX release process.
Communicate release blockers
Categorized bugs board
[Adolfo]: Working on an official proposal for automating the sync between the testing spreadsheet and GH.
Security
[Peter]: Confirming and documenting the process for reporting security issues during the release process.
Backports
[Majo]: Improving how we handle backports and the information radiators we use.
[Jorge]: Creating and publishing a backports policy including old releases PRs.