Hi all, Below is an AI-assisted note summary from today's CSC weekly meeting. Best Regards, Dan Release Updates - "V" Release Name: The 'V' release name has been unanimously voted and approved as Vampire. - v20.2.1: On track to release before the squid window closes and tentacle opens (target date in community calendar is March 18). - v18.2.8: Looking good with only minor blockers (a critical FS perf issue was merged last week). However, expect speedbumps due to logistics of moving to the new QE infrastructure. - Note: The team is exploring modern solutions for signing releases (e.g., using Hashicorp Vault's transit signing for containers with cosign). This discussion will move to the Release Engineering meeting. - v19.2.4: There hasn't been much movement here. Please do not wait until the last minute. Branch & Merge Policies - Merging to EOL Branches (reef): There was a discussion on whether to keep the reef branch open for merging useful vendor PRs, despite being EOL. There were mixed opinions regarding the extra team workload versus vendor utility. No consensus was reached; the discussion will continue in the Release Engineering call. - Pre-Merge QA Policy: Brought up due to recent confusion over a PR merging before the bulk process was completed. Generally, PRs should be batched to avoid overloading the lab, rather than authors performing their own QA runs and merging based on those results. Discussion to continue next week. Access & Committer Management - Trimming ceph.git Committers: A recent merge bypassed process and broke the manager. We currently have over 200 people with merge access. - While trimming will be contentious, many users only need access for minor issues like labeling, which could be solved with fine-grained permissions. - Action Required: If you know of specific users who no longer need access (e.g., no longer working on Ceph), please bring those examples to the group. - Discussion on trimming members and updating merge rules (e.g., CODEOWNERS) will continue next week.