Ubuntu Landing Team

The Ubuntu Landing Team is a group of people managing releases of new packages through CI Train, deciding on Touch image promotion, tracking quality of Ubuntu Touch images and related. The Landing Team consists of people from various teams such as Phonedations, Foundations, QA, CI, Community with a common goal of getting high-quality Touch images with proper development velocity.

Documentation

Please make sure all involved parties have familiarized with the following documentation topics.

For Landers

• citrain/LandingProcess - a basic guide to how to land things through CI Train

• LandingTeam/MilestoneSchedule - schedule used for every milestone in the ubuntu-rtm distribution

• LandingTeam/Smoketesting - overview of all the different dashboards used for automatic autopilot testing for every image

• citrain/RTMLandingApproaches - overview of approaches for landing your changes to Ubuntu RTM

• citrain/FAQ - frequently asked questions regarding the landing process

For Landing Team members

• LandingTeam/LandingTeamProcess - an overview of how the Landing Team works and manages their workflow

• citrain/ComponentSupportList - list of upstream contacts per components

• LandingTeam/IncidentReports - documentation of each TRAINCON-0 incident

Other

• LandingTeam/SiloTestingGuidelines - guidelines for testing silos prior to approving them for landing

• LandingTeam/TouchChannels - overview of the image channels that we have available

• LandingTeam/SupportedDevices - a quick look on the supported devices during promotion for specific channels

Useful Links

• The CI Train Dashboard - the main dashboard that should be used by landers to manage their silos (building, managing)

• The CI Train Spreadsheet - the CI Train backend spreadsheet, used for submitting new landing requests and communication

• QA Silo Sign-off Trello Board - trello board used to keep track of which silos are being currently signed off and to keep track of what the QA team is working on

• Landing Team Issues Tracker - an early version of a simple interface for tracking blocking issues coming from the Landing Team

Members

Landing team members change over time, so the list might not always be up-to-date.

• AlanPope (core-apps)

• BarryWarsaw (US-tz CI Train support)

• BrendanDonegan (QA)

• ColinWatson (UTC-tz CI Train support)

• DaveMorley (QA)

• LeoArias (QA)

• LukaszZemczak (UTC-tz CI Train support, current landing team lead)

• OliverGrawert (phonedations)

• PaulLarson (CI)

• RobertPark (US-tz CI Train support)

• SivatharmanParameswaran (CI)

• StephaneGraber (US-tz CI Train support)

• TimoJyrinki (UTC-tz CI Train support)

Sheriff Schedule

These people are responsible for helping you assign & publish silos at these times. If no sheriff defined, please ping trainguards in general:

IRC

General landing discussion takes place in #ubuntu-ci-eng, in which queuebot will ping frequently about the progress/statuses of various silos. Landers should set an IRC highlight for "trainguards" if they want to follow when to assign or publish silos for people. Be warned though that this gets pinged frequently throughout the day.

If you need help troubleshooting a problem with CI Train, you should contact the Sheriff in #ubuntu-ci-eng, as per the above schedule. The channel topic should also indicate who the current sheriff is. When in doubt, many sheriffs have their IRC highlights set for "trainguards" so you can reach a timezone-appropriate person that way as well.