2023-06-26 BTR Meeting Minutes

5 min

Palm.2

@Jorge Londoño

Palm.2: Wed 2023-08-09

• Review the board over the coming weeks

• We have two months

10m

Know issues

@Peter Pinch

What should “known issues” mean in the release notes? From a comment on

• Include the issue mentioned mentioned above

• @Adolfo Brandes suggests a criteria: if somebody says they can’t upgrade to the release in question because of a bug, we should add that to the known issues section

• @Peter Pinch will word a response to what is the criteria

Rename release branches?

@Ned Batchelder (Deactivated)

• @Ned Batchelder (Deactivated) suggests we should do some discovery on this:

  • What is the new naming scheme?

  • Is it available?

  • How do we execute the migration?

  • When do we execute the migration? (Probably not in the last month before Quice)

• We need an owner: @Jorge Londoño will reach out to @Régis Behmo to ask if he’d like to lead this effort
  

Palm Post-mortem

@Peter Pinch

• @Jorge Londoño will be in charge of leading the retro, will announce in Slack or Discuss

Quince MFEs

@Peter Pinch

• Learner Dashboard

  • Depends on a maintained credentials Tutor plugin; Edly has seemingly picked it up

• Learner Record

  • Depends on upstream being included in maintainer’s pilot (plus merging fixes)

• Publisher?

• Support tools?

• Studio?

  • Being added to frontend-app-course-authoring as we speak; we might get some experimental pages by Quince

Inconsistency in feature flags

@Peter Pinch

• Some are controlled by Feature Flags, some by Waffle Flags, and some have dedicated settings

• If it’s properly annotated in the code it should appear in the technical documentation

  • We’re not sure, though usually Waffle Flags do work

  • @Ghassan Maslamani will ressurect an old PR to restart this conversation

  • Some omissions in the output docs. Example.

• @Ghassan Maslamani suggests updating OEP-17