Request for Comments: Redwood Release Testing Strategy - Your Input Needed!

:wave: Dear BTR WG and Open edX Community members!

We are excited to present to you the draft proposal for the Redwood Release Testing Strategy, which is the result of the increasing engagement of the Product Working Group, led by @jmakowski, with the Open edX Community release processes, an ongoing effort that started a month ago with the first Redwood Meeting Planning. An effort whose sole objective is to benefit our end users and the community in general by having a clearer, more coordinated and impactful release process. We are eager to gather your feedback and insights to ensure that the proposed changes align with the needs and expectations of the Community and, especially, of the BTR, the group of people who have successfully been in charge of this process for several years already.

:heart: Why Your Feedback Matters: The Redwood Release Testing Strategy proposal outlines several key recommendations aimed at enhancing the efficiency and effectiveness of the release testing process. However, we recognize that these proposed changes may represent significant changes to the process that the current BTR WG members follow for each release. Therefore, we are reaching out to you to seek your input and perspective on the proposed strategy.

:window: Openness to Community Feedback: We want to emphasize that we are open to adjusting and prioritizing the set of recommendations included in the proposal based on the feedback we receive from the community. We understand that some of the proposed changes may represent a departure from current practices and may require a significant effort to implement. As such, we are committed to identifying an MVP based on community feedback and gradually transitioning to the full set of recommendations over time.

:bulb: How You Can Contribute:

  1. Review the Proposal: You can access the draft proposal here. We encourage you to review it carefully and share your thoughts, concerns, and suggestions.
  2. Provide Feedback: Whether you have questions, concerns, or ideas for improvement, we want to hear from you. Please feel free to reply to this post or reach out to us directly with your feedback.
  3. Spread the Word: We encourage you to share this post with other community members who may be interested in contributing to the discussion. The more diverse perspectives we gather, the better equipped we will be to make informed decisions.

:clapper: Next Steps: After collecting feedback from the community, we will carefully consider all input and work towards identifying and prioritizing the most urgent improvements based on the Redwood Release Testing Strategy recommendations. Given our timeline to start working on the Redwood release in April, we aim to finalize the selection of recommendations for implementation by the end of February. This will allow us enough time to review the feedback, prioritize the action items, and begin preparations for the upcoming release. We are committed to transparency and collaboration throughout this process and will keep you informed of any developments.

We extend our sincere gratitude to each and every one of you for your ongoing support and contributions to the Open edX Community releases. Your participation in this feedback process is invaluable, and we truly appreciate your time and effort. We are all aware of the current context that the community is facing and, personally, I believe that this proposal takes us in the right direction. The direction of being a stronger, more coordinated, and empowered community in control of its own future.

Side note: I would like to draw the attention of some specific members of the BTR to this post, who have had very active participation in the last release processes. We’re keen to hear your thoughts on this matter, @regis @mgmdi @pdpinch @nedbat @Dean @sambapete @ghassan @Maksim_Sokolskiy @mtyaka @arbrandes


Thanks @jalondonot! Lemme just add a thought, in the way of clarification: that page is less a unified proposal, and more a collection of suggestions. They’re meant to be picked from, based on how valuable and doable each is judged to be.

For instance, it could be decided that reducing the testing window makes sense, but is just not doable by Redwood. So we drop that, but keep the Product-owned testing sheet.

(I still think we should try pushing the cutoff from master forward some, though. :stuck_out_tongue_winking_eye: )


As a follow up, I’d like to share a prototype for what we mean with our proposal that Product takes responsibility for the Testing Spreadsheet, namely writing tests, aligning tests/features to the core product, and providing input on prioritization.

We’ve put together a prototype to help illustrate what we mean by all of this. I’ll be happy to discuss in more detail at the next BTR meeting, or asynch via comments on the sheet. Prototype: Product Responsibilities on the BTR test list - Google Sheets


When testing a feature, I think it should at least be tested in Desktop web browsers, mobile web browsers, and mobile apps. If testers have time, they can consider testing in iOS and Android apps and web browsers. That’s how we usually test our software.
The current mobile web browser experience is terrible when learners have notifications in the notification tray or the discussion sidebar is on.

1 Like

Hi folks! To identify and prioritize the recommendations to be implemented for the launch of Redwood, I am launching the following poll in which you can select the recommendations from the Redwood Release Testing Strategy that you consider could add value in the immediate or short term to the process of releasing a new version of Open edX. This will allow us to perform a first iteration and evaluate after the release of Redwood the impact of the implemented improvements and weigh whether we should continue to implement improvements for future releases. The information we collect here will help us make decisions during the next BTR meeting to begin preparations for the testing phase after Redwood is cut in approximately 6 weeks. You’re more than welcome to join us!

  • 1.The Product Core Working Group should take ownership of a “master” test spreadsheet
  • 2.Cut the official testing period in half
  • 3.Codify the process on Open edX Documentation
  • 4.Move from spreadsheet to Github issues
  • 5.Process suggestions
  • 6.Make the test plan/state more visible/discoverable
  • 7.Milestones (with dates) should be set
  • 8.Maintainers are responsible for fixing bugs or getting the authors of the feature question to do so
0 voters

Based on the poll results the BTR has decided to implement recommendations number 1, 8, 5, 3, 7, 4, and 6, from the Redwood Release Testing Strategy (Draft) to the current release testing process. Since there was no quorum, at the 04/03 meetup, for deciding on whether to implement recommendation number 2 (Cut the official testing period in half) or not, we’ll keep the conversation open in Slack to make a final decision in the next session.