2024-03-04 BTR Meeting Minutes

Date

Mar 4, 2024

Participants

@Jorge Londoño
@Chelsea Rathbun
@Jenna Makowski
@Peter Pinch
@Adolfo Brandes

🎥 Recordings

Discussion topics

Time	Item	Presenter	Notes	Action Items

Item	Presenter	Notes	Action Items
Newsletter	@Jorge Londoño
Follow-up on action items of previous meeting @Jorge Londoño will confirm the current BTR roles assignees' (Build-Test-Release (BTR) Working Group \| Membership ) interest on continue their commitment for Redwood. @Jorge Londoño will create a multiple choice poll in the previous post Request for Comments: Redwood Release Testing Strategy - Your Input Needed! for getting a sense of the community approval or rejection to each of the points of the Redwood Release Testing Strategy.	@Jorge Londoño	BTR roles assignees: Group Chair: @Jorge Londoño (edunext) Release Manager: @Maksim Sokolskiy (Raccoongang) Release Testing Coordinator: Vacant Quality Assurance Manager: Vacant Release Documentation Expert: @Chris Patti (MIT Open Learning) Bug Triagers: @Maria Grimaldi Security Patcher: @Maga Jaimes Poll results:	@Jorge Londoño will post a call for help in the Community channels for filling the vacant BTR roles. @Jorge Londoño will post the proposal for postponing the cutting date 2 weeks and holding a meeting to deciding if, based on the input from the Product WG, we can cut the release on the set date or we can wait one sprint more for landing more features to the specific release.
	@Jenna Makowski		@Jorge Londoño will ask the BTR team to review the prototype and provide feedback. @Jenna Makowski and @Chelsea Rathbun will keep filling the spreadsheet until the new Testing Coordinator is designated to start coordinating the work with him/her.

Decisions

Based on the poll results ( ), the BTR has decided to implement recommendations number 1, 8, 5, 3, 7, 4, and 6, from the to the current release testing process.
Since there was no quorum 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.