...
Sarina Canelake poorly playing the notetaker role
🎥 Recording
🤖 AI-Generated Meeting Summary (Unedited)
Quick recap
The team discussed the status of testing, including unassigned tasks, the function of certain features, and the complexities of upgrading software versions. They also addressed issues related to language settings, translation processes, and system regressions, with plans for further investigation and resolution. Lastly, they reviewed open issues related to test reports, prioritized release testing issues, and discussed frameworks and release notes.
Summary
Test Progress and Deployment Updates
Peter reported that 95% of the tests were completed and he was in the process of identifying the remaining incomplete ones. Max added that he needed to retest some items and would mark them up accordingly. Max also mentioned that the Android Plugin was not yet deployed and he would provide an update on its status. Lastly, Peter pointed out that there were some unassigned tests that needed discussion, as no one had volunteered to do them.
Investigating 'Waffle Switch' and Grading Features
Peter questioned the function of a 'waffle switch' for enabling global staff optimization and the 'grading switch assume 0 grade if absent' feature. María explained the former's legacy usage for performance and course optimization, while Peter speculated the latter's purpose for maintaining backward compatibility with a grading system change. Max agreed to investigate both features further. Additionally, Peter raised concerns about a test concerning the upgradability of major software versions, which Sarina suggested should be tested for operators with previous versions. It was decided that Max would also look into this.
Sandbox Strategy and Upgrading Challenges
Peter, Sarina, Adolfo, and Max discussed the current sandbox strategy for testing the new software with an existing installation, and the complexities of upgrading from Quince to Redwood. Adolfo suggested that the upgrade should ideally be tested in a separate, dedicated sandbox, and proposed reaching out to Fayaz, who has been doing a lot of the testing for Edly, to comment on the process. Sarina raised the idea of establishing a more permanent sandbox for continuous testing and data collection, and suggested that the team should consider appointing a Tutor Maintainer for each release. This idea was agreed to be worthy of further discussion.
Unassigned Testing Tasks and Mfe Issue
Peter discussed the remaining unassigned testing tasks, specifically those related to LTI and Grade pass back, which he planned to follow up on. Adolfo and Sarina then delved into a release blocker issue regarding language change behavior in the MFE, which they classified as a longstanding bug rather than a blocker. They agreed to investigate this issue closely, given its potential impact on user experience.
Language Support and Translation Issues
María, Max, Sarina, and Adolfo encountered an issue where the language setting did not affect the displayed language on the page. They explored various language options, including Hindi and Polish, but found that the issue might be related to the availability of translations for certain languages. They also discussed the discrepancy between the number of translations for French and French Canadian. Sarina suggested checking with Brian Smith about this issue, and Adolfo highlighted the need to ensure the supported languages are included in the language JSON. The team decided to revisit the language support before finalizing the release.
Language Switcher and Repository Alignment
The team discussed issues related to their current setup and translation process. Max presented a working language switcher from a recent installation, which María agreed to test. Sarina expressed concerns about the lack of alignment across the 22 separate repositories, suggesting this could be a topic for a future working group. Adolfo agreed, indicating that he no longer trusted the current system due to its complexity. Finally, María mentioned that Brian had been assigned to address another issue, although it was unclear if he was currently working on it.
Regression Analysis and Investigation Plan
María identified a regression in the system, specifically in three areas: content availability, sidebar functionality, and limited staff access. She mentioned that content availability was previously restricted when a course was self-paced, but this limitation was no longer present. However, there was an issue with the sidebar displaying incorrectly and, concerning limited staff access, although a permission denied message appeared, users could still create certificates, but not perform other actions. Adolfo agreed to investigate these issues, with assistance from Max.
Test Issues Review and Prioritization Process
María reviewed the open issues related to test reports and repositories. She explained her process for identifying and reporting issues, and how she prioritizes them. Adolfo clarified the two views of the board: one for release testing and another for test reports. María confirmed that not all issues need to be reviewed in both views, as long as there's a link to the test report if it's related. She also expressed the need for help in solving these issues due to bandwidth constraints. A follow-up meeting was planned to address any remaining issues before the next release.
Prioritizing Test Issues and Upgrades
María asked Chelsea to assist in prioritizing release testing issues after lunch, which Chelsea agreed to. Sarina shared her plan to update product release notes and rearrange the site's front page for clarity. An action item was assigned to Mia Delpho or Brian Smith to address a language issue. Adolfo offered his help for any unexpected release blockers that might arise during the week, while Peter would discuss the upgrade issue with Eddie. The team agreed to focus on the 'test failures' view and to ensure no release blockers were missed.
Framework Review and Release Notes Coordination
Chelsea, María, and Sarina discussed a framework developed by Jenna and agreed to review it together after stand-up. Sarina offered to assist Chelsea with the release notes, indicating that she would follow up via Slack. Christopher shared his understanding that he would handle the operator side of the release notes once Sarina had completed the product side. María expressed her intention to update the waffle flags in the Redwood settings, a task Sarina said was important as not everyone remembers to document their waffle flags on the Wiki page. Finally, Sarina thanked María for her work on the board and suggested endorsing María for product management on LinkedIn.
This summary captures the essence of the discussion, the participants involved, and the decisions made during the BTR meetup but does not intend to be as accurate as a transcript. If you notice any inconsistency, please report it by creating a comment in the part of the text that is incorrect and notify Jorge Londoño.
\uD83D\uDDE3 Discussion topics
...