@Andrés González posted the call for testers on Friday, only one issue reported (not a blocker).
Sumac Sandbox
@Jenna Makowski asked about how to track missing configurations in the sandbox.
Indigo theme test failure report
@Maria Grimaldi highlighted an issue with the Indigo theme’s copyright inconsistency in testing reports.
Indigo theme’s use as the default theme needs further discussion.
@Jenna Makowski noted that Edly, as the creator, must approve its use under open source licensing if it’s to be the default theme.
New features testing
@Chelsea Rathbun is adding tests for aspects.
Smoke tests were added to verify headers across Studio and LMS, feedback welcomed.
Documentation
@Chris Patti is compiling release documentation and coordinating testing in in-house CI environments.
Release Management
@Maksim Sokolskiy and @Farhaan Bukhsh working on release blockers and the role transition.
Header Slots
For the header plugin slot, I (@Chelsea Rathbun ) added a few basic smoke tests to make sure for the user the header appears as expected on Rows 27-32 on the testing spreadsheet since we’ve added new plugin slots for those users that haven’t updated the header using the new header plugin slots. Did I miss any headers on the platform we should add tests for?
Plugin slot testing
@Brian Smith raised the need for an additional testing environment for header slots plugins, as modifying the main sandbox would disrupt its operation.
@Maria Grimaldi will summarize the discussion on the indigo theme ticket.
Consensus was reached to have a secondary sandbox for experimental testing of plugins.
@Chelsea Rathbun and @Brian Smith to coordinate on writing test cases for fake plugins to ensure slot functionality.
Nomination for a new Release Manager
@Maksim Sokolskiy
As a group we agreed on the following:
Nomination can be made by the person currently holding the role, but they are not expected to do so
The appointment of a new person to the role must be made by the group Chair
The new person can make the nomination in person
Switch to a release/sumac.masternaming
@Maksim Sokolskiy
As a group, we have decided not to switch to the new naming in the middle of the testing period and to postpone the change to Teak. Changes will be planned accordingly.