Cedric started a discussion on the meeting recording. The ask is to make the meeting recording available to the community. The current policy is to have the recording only available for a week to ensure minutes can be completed. Note: Many public meetings are recorded for a short time to help with editing and creating minutes. Suggestion: If there is a need to change the recording policy, it should be brought forward as a proposal to the next TSC meeting.
Concern that M3 (contents freeze) is very "early".
Need to clearly explain as part of the schedule that specification is working on release "n+1" whereas validation and testing is on release "n"; i.e. there is no dependency between specification work and testing/validation work.
Pankaj will propose some changes to the current schedule to allow for better interleaving of specification and testing/validation development work.
Gergely to add the topic to the agenda of the technical meeting on Monday.
NOTE: Meeting times are nailed to UTC. With the US switching to DST this weekend and Europe 2 weeks later, meeting times are a bit out of synch. Gergely will propose a meeting time for the next 2 technical meetings → look for an email from Gergely.
Can Anuket stay on same version during a release (6-months) or control new features we adopt? For GItLab.com SaaS, version upgrades occur automatically behind the scenes. We use CI/CD to release fixes/improvements and enable access to new features as quickly as possible for users of our SaaS service. New versions are tested and go through a QA process before being deployed to GitLab.com to ensure quality and backward compatibility. In other words, version upgrades on GitLab.com should not break any functionality in terms of web interface, command line interaction, or API functionality.
5 min
Status Updates
Linux Foundation Lab (Portland) hardware upgrade status