2024-12-02 BTR Meeting Minutes

 Date

Dec 2, 2024

 Participants

  • @Maria Grimaldi

  • @Adolfo Brandes

  • @Andrés González

  • @Chelsea Rathbun

  • @Dave Ormsbee (Axim)

  • @Farhaan Bukhsh

  • @Jenna Makowski

  • @Jorge Londoño

  • @Maksim Sokolskiy

  • @Peter Pinch

  • @Sarina Canelake

  • @Syed Muhammad Dawoud Sheraz Ali

🎥 Recording & Chat

 Discussion topics

Time

Item

Presenter

Notes

Action Items

Time

Item

Presenter

Notes

Action Items

 

Newsfeed

 

 

 

Redwood retrospective action items follow-up

 

 

 

 

Sumac

1. Release Blockers

  • Programs URL in Header:

    • The issue with configuring the programs URL in the learner dashboard header has been resolved. A new environment configuration option has been introduced.

    • The fix is merged into the master branch, but a backport PR may still be needed to include it in the Sumac release.

    • Team emphasized the importance of documenting this update in the release notes to inform users about its behavior and configuration.

  • Release Notes Issue:

    • The docs build problem caused by Sphinx checking dummy URLs has been fixed. Farhaan clarified the root cause and confirmed the fix applies to both master and Sumac branches.

    • However, automating the generation of waffle flags and other settings changes for inclusion in the release notes remains unresolved.

    • Chris plans to address this after returning from Thanksgiving break, with Maria offering additional support.

    • The team discussed the criticality of this section in the release notes. Maria will follow up with Chris to provide help if needed.

  • New Sidebar Navigation:

    • Discussions focused on whether to enable the new left sidebar navigation by default for users upgrading from Redwood.

      • Current behavior: Existing installations must manually enable the feature.

      • Proposed change: Automatically enable the feature for upgraded users while maintaining a fallback option to disable it.

    • Concerns:

      • Potentially overriding intentional configurations by users who previously disabled the feature.

      • Ensuring proper communication in the release notes about this change and the eventual deprecation of the legacy navigation.

    • Action items:

      • Add a manual upgrade command to enable the feature as a transitional measure.

      • Prepare a deprecation notice for the legacy navigation, targeting removal in an upcoming release.

  • Forums v2:

    • The new discussion forums feature, which transitions from MongoDB to MySQL, is ready for inclusion in Sumac.

    • Testing in the sandbox has been successful. Pending merge conflicts on related PRs are expected to be resolved within the week.

    • For existing installations, forums will remain on MongoDB for now, with MySQL used only for new installations.

2. Testing Process

  • Progress Update:

    • Completion rate: 83.9%.

    • Some tests are unassigned or pending setup for specific configurations (e.g., single sign-on).

    • Maria volunteered to handle single sign-on tests; Andrés and Adolfo to assist with other pending tests.

  • Sandbox Issues:

    • Outline generation failing for demo courses; root cause investigation underway.

    • This is a high-priority issue as it blocks further testing.

  • Mobile Testing:

    • Discussions on including mobile application-related tests; a sandbox for mobile is available.


3. New Features Testing

  • Plugin Slots:

    • Header updates verified; plugin slots are ready for testing in the sandbox.

    • Coordination with plugin maintainers needed to finalize integration.


4. Release Management

  • Forums v2:

    • Ready for inclusion in Sumac; pending resolution of merge conflicts for final PRs.

    • No blockers anticipated.

  • Tagging Responsibility:

    • Farhaan confirmed readiness to handle tagging for the release.


5. Debugging

  • Prioritization:

    • High-priority issues reviewed; prioritization to be finalized by Chelsea and Jenna.

    • Ongoing triage to identify additional potential release blockers.

Next Steps

  • Testing and Bug Fixes:

    • Team members to pick up unassigned tests and high-priority issues.

    • Additional tests to be coordinated across teams for better coverage.

  • Follow-Up Meeting:

    • Scheduled for Thursday, December 5, 2024, to review progress and remaining blockers.

 

 

 

 

 

 

 

 

 

 

 

 Decisions

  •