Portal:Toolforge/Admin/Monthly meeting/2026-06-30
Appearance
Attendees
Bryan Davis (bd808), Chris Ciufo, David Caro, Francesco Negri, Raymond Ndibe, Seyram Komla Sapaty, Sohom Datta
Notes
- phab:T424362 Define update process for Toolforge builder/runner images
- For small versions bumps:
- Should we keep offering two versions?
- We'll keep a 1-month stable version
- We'll keep a “latest” which is up to date with what's offered upstream by Heroku
- How do we update them and how often?
- Stable version is always 1 month old, so updated monthly
- Latest will be updated weekly
- One issue is testing compatibility with all the languages we support
- We'll trust the “field test” of tools which are set to use the latest version
- Should we keep offering two versions?
- For ubuntu version bump (e.g. heroku-24 to heroku-26)
- Halt all small version bumps for some time (while the ubuntu version bump is ongoing)
- Follow the same process as last time (phab:T380127#11696394)
- For small versions bumps:
- Standard items:
- k8s upgrade workgroup progress
- We are already 2 versions behind
- Should we keep upgrading the versions constantly through the workgroup?
- Yes, at least until we figure out a different process
- phab:T194332 Push to deploy beta
- Fixes have been added to jobs-api
- Work in progress on the refactor and adding webservices on top
- Working on a patch to allow to buffer the builds and not fail if the build queue is full
- Tools Platform will revisit the timeline and publish a plan for the next release phase
- Sustainability score
- After the publication of the initial assessment, we’ve closed the related KR for now.
- We are looking to aggregate all related tasks, I believe the next two quarters.
- This will possibly involve the continuation of individual tool reviews for: osi-approved license, tool metadata, source code publication, not load external resources
- Send reminders to the community this meeting
- Let's try it out and make sure we moderate the discussion
- Update the wiki page to set overall meeting purpose
- Discuss potential of office hours for the team to provide support contributors
- Channels: mailing lists (cloud, cloud-announce) + `wikimedia-cloud` on IRC (1 week before)
- phab:T430120 Bug in Striker due to Phabricator upgrade
- Patch available, needs a review
- Is there a staging environment to try it out?
- There should be striker in tools-beta
- We can look into adding Striker to lima-kilo so it can be part of our integrated dev environment
- k8s upgrade workgroup progress