I. Context, data, and highlights 🏅
The Product Working Group was closely involved in the process and led the implementation of several changes to it (Redwood Release Testing Strategy ), including:
Monthly meeting to track new features and initiatives to be included in Redwood (https://docs.google.com/spreadsheets/d/1tWgp9LXNg4sfWYd_0ghNl6qfIZZ9851MtGBXPeSgzFs )
The Product Core Working Group should take ownership of a “master” test spreadsheet of new features
Maintainers are responsible for fixing bugs or getting the authors of the feature question to do so
The Redwood master branch was cut on 09/05 as planned.
The official testing period was cut in half to increase the chance of landing more new features in Redwood. For this reason, the testing process was launched on 16/05 (https://discuss.openedx.org/t/join-the-redwood-testing-team/13017 ).
Due to a last-minute security vulnerability (https://discuss.openedx.org/t/security-upcoming-security-release-for-edx-platform-on-2024-06-17/13204/3 ), Redwood was delayed a week and a half, to be successfully released on 19/06.
To target their respective audiences more specifically, the release notes were divided into https://docs.openedx.org/en/latest/community/release_notes/redwood/feature_release_notes.html and https://docs.openedx.org/en/latest/community/release_notes/redwood/dev_op_release_notes.html.