Build/Test/Release Working Group Biweekly Meetup

Today’s meeting, which mostly involved going through the list of issues remaining for Lilac.1:

1 Like

I suggest we discuss the following on our meetup today:

  • Lilac.1 retrospective
  • Volunteers for chairing the group for Maple

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

1 Like

Apologies for the delay! Here’s the recording of the meetup on 2021-06-21:

1 Like

This is the plan for today:

  • Finding a chair for Maple
  • Finishing the Lilac.1 retrospective
  • Lilac.2
  • Bounties, Open Collective, and the future

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

Aaand today’s meeting:

Today’s agenda:

  • Validating @BbrSofiane as the new chair
  • Starting to fill roles for the Maple release cycle
  • Learning MFE discussion
  • Cleaning up the board.

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

Can we add an agenda item? We’ve been trying to get the Learning MFE working in master. We’ve found and solved multiple issues, but we currently blocked by an authentication problem that we can’t solve.

1 Like

Today’s meeting:

1 Like

Today’s agenda

Role assignments

Lilac.2

Maple

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

1 Like

I’d like to add to the agenda the following questions, which can be tackled over one or more sessions:

  1. Are there blocking issues for the adoption of Tutor as the default community installation? If more time is needed for investigation, what is the deadline and who is in charge for handling this task?
  2. If Tutor becomes the new default community installation, what changes to the current release process do we need to make? I’m thinking in particular in terms of CI/CD.
  3. Do we need to make organizational changes to the Tutor maintainers program? Currently, maintainers are the ones making decisions about the future of Tutor. How do we avoid duplicate discussions with the BTR group and make sure that we can reach decisions swiftly, all the while guaranteeing that the ones making decisions are actually contributing back to the project?
3 Likes

Meeting notes from 2nd august 2021

Role Assignments

Roles have been assigned as follows

Release Manager - @regis

Release Documentation Expert - @pdpinch

Release Testing Coordinator - @jhony_avella

Bug Triager - @arbrandes

Community Liaison - @dbates

Lilac 2 release date Week of 16 August currently 8 outstanding items

Action Items Owner(s) Deadline Status
74 MFE Ecommerce workflow back compatibility TBA @arbrandes is checking with open craft moved for potential ownership and timeline moved to liliac3 at earliest most likely Maple
79 Release update issue 02/08/2021 Update or change to bot required to push updates to release to be checked on
85 @BbrSofaine tba Moved to lilac 3
36 Moved to maple
89 @arbrandes +@dbates Create ADR for change
90 # @BbrSofiane Add PR to Edx Configuration
9 @sarina Could be an internal EDX team holdup to be chased to find reasons for problem not a blocker issue
69 @ned May already be fixed

Internal actions for Maple

Approximately 77 open issues in JIRA to be dealt with by the BTR community so the delegation of work loads will try to clear at the rate of 7-11 per week. We will work to coordinate that with both the community and edX team in need to include the core contributors to assist with more of the development and testing.

Improvements in working:

Develop a relationship between edX and the community around problem solving and shared ownership.

improve and refine ways of working to help the community play a role in refining delivery and finding solutions in an asynchronous way for Maple release as well as automation tools for release.

2 Likes
  • Lilac.2

  • edx-certificates

  • Learning MFE

  • Kyle McCormick to speak about what it would take to have Learning MFE in Maple

  • Tutor

  • If Tutor becomes the new default community installation, what changes to the current release process do we need to make? I’m thinking in particular in terms of CI/CD.

  • Do we need to make organizational changes to the Tutor maintainers program? Currently, maintainers are the ones making decisions about the future of Tutor. How do we avoid duplicate discussions with the BTR group and make sure that we can reach decisions swiftly, all the while guaranteeing that the ones making decisions are actually contributing back to the project?

  • What other services are missing?

  • How do we aggregate tutor plugins?

  • Django 3.2 Upgrade

  • Weekly target for the group

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

Today’s agenda

Lilac.2

Maple

  • Django 3.2 Upgrade

    • First deadline on the 31st of August
  • Learning MFE - @kmccormick

  • Tutor

    • What other services are missing? How do we aggregate tutor plugins?
    • What changes to the current release process do we need to make? (CI/CD)
    • Do we need to make organizational changes to the Tutor maintainers program? Currently, maintainers are the ones making decisions about the future of Tutor. How do we avoid duplicate discussions with the BTR group and make sure that we can reach decisions swiftly, all the while guaranteeing that the ones making decisions are actually contributing back to the project?

Meeting URL: Launch Meeting - Zoom
Meeting ID: 895 7565 8344
Passcode: btr

Minutes and recordings for BTR Working group Biweekly meetup August 16 2021

Recordings

Minutes

the next meeting will be on August 30th 2021 at 15:00 UTC

Meeting location information to follow

If you have any issues or comments with the minutes please reply to this post

3 Likes

Working group meeting location change
As previously discussed we are relocating the Build Test Release group meeting to a new zoom meeting location. Thanks to @Adolfo for all his work in hosting and recording the meetings in the past.
The new meetings continue to occur on alternate mondays with the next one being August 30th 2021 at 15:00 UTC please translate to your local timezone.
The new meeting details are
Meeting Via Zoom
Topic: open edX BTR Working group
Time: 15:00 UTC
Meeting ID: 940 1700 7402
Passcode: btr
Direct Zoom link

I will record and post the recording as soon as possible after the meeting.

BTR Working group Calendar invitation

Today’s agenda

Lilac.3

Maple

2 Likes

Is there any recordings of this meetup? @BbrSofiane

Keep up the great work!

Meeting notes from BTR Group Augst 31 2021

I want to apologise to everyone on the lateness of this it was a case of after some surgery It took a little longer to recover from some complications than I had hoped.

The meeting information is below

2 Likes

Today’s agenda

Lilac.3

Maple

Meeting notes for BTR working group Sept 13 2021

Any updates changes or otherwise please contact me

2 Likes