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/LandingOther - how to proceed with landing changes for non-standard packages, like clicks and tarballs (mostly valid for the overlay)

• LandingTeam/ReleaseSchedule - schedule used for every OTA stable update

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

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

• Touch/BugManagement - information on how to escalate bugs to the Product Team and getting them approved for the rc-proposed/stable channels

• citrain/SyncSilos - documentation regarding the silo sync functionality

• LandingTeam/StagingClicks - staging clicks depending on new frameworks in the store and images

For Landing Team members

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

• LandingTeam/TrainguardDuty - details regarding our Landing Team trainguard duty, handling emergencies and how to keep the train always running

• LandingTeam/Procedures - a list of step-by-step procedures for several common/uncommon situations that usually require LandingTeam action. This should be the first place to check in case the LandingTeam lead is not around but a typical infrastructure task needs to be done.

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

Obsolete

• LandingTeam/IncidentReports - detailed reports of each TRAINCON-0 incident - no longer used as we have a different release model now

• LandingTeam/MilestoneReports

Useful Links

• The CI Train Landing Requests - the main CI Train page used for managing landing requests

• 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

• Touch Version Decoder Ring - useful web tool for fetching versions for different touch channels

Members

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

• AlanPope (core-apps)

• DaveMorley (QA)

• JeanBaptisteLallement (QA)

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

• RobertPark (foundations, US-tz CI Train support)

• TimoJyrinki (SDK, UTC-tz CI Train support)

• VictorRuiz (QA)

IRC

General landing discussion takes place in #ubuntu-ci-eng, in which queuebot will ping frequently about the progress/statuses of various silos. Landing Team Members 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 ping trainguards in #ubuntu-ci-eng.