2022-07-18 BTR Meeting Notes

~(5-10)min

Backport i18n string to nutmeg

 @Ghassan Maslamani

Due to syncing glitch between TX and edx-platform. Nutmeg lost about +3 months of translation work. To resolve I suggest to backport strings to nutmeg so those can be used but this might be dangerous.

PR chore(i18n): update translations (#30383) by ghassanmas · Pull Request #30733 · openedx/edx-platform

~(5-7)min

Course author MFE with tutor mfe

@Ghassan Maslamani

Any guideline about running the course MFE with tutor… any flags needs to be set?
Add to that course author MFE would be the first MFE (to my knowlege) that makes RESTful calls to CMS i.e CMS_HOST in tutor.

5min

Who should be tagged for review when merging to release branches?

@Kyle McCormick

I took a guess when I updated this page: Backporting: Making a pull request for a named release | Making a change that also belongs on master (a “backport”)

I wrote essentially: “release manager review required; team member review appreciated”

5-10min

Release names: What’s after “Olive”?

@Kyle McCormick

I’ve heard both “Palm” and “Poplar” floating around.

• “Palm” is on the chart: Support Windows, it’s in honor of eduNEXT, since the Palm is the national tree of Colombia.

• BUT: what after that, and who should decide?

5-10min

Product Working Group alignment

• In what ways can BTR collaborate with the newly formed Product Working Group?

• Where do our areas of interest or responsibility overlap?

• How do we foresee our relationship with Product?

1 min

Nutmeg Retrospective

@Sofiane Bebert (not attending)

For the next meetup, can BTR member share they thought on the Nutmeg Release process on this board: EasyRetro | Improve your team with fun sprint retrospectives