RecognizedFlavors

Revision 2 as of 2011-11-02 03:51:17

Clear message

*** DRAFT FOR DISCUSSION ****

Resources and Services that Canonical provides for Recognized Flavors:

Infrastructure

  • status.ubuntu.com for work item tracking at flavor and individual level.
  • launchpad mail list support for project communication.
  • Ubuntu Security team will help the flavor maintainers distribute security updates to their users, by reviewing any sponsoring any updates they wish to provide.
  • Notification of vulnerabilities can be provided by Ubuntu Security team to flavor maintainers, if universe package list to monitor is provided.
  • Minimum of 1 person gets sponsored at UDS

Daily ISO build and publish

  • Use of launchpad build infrastructure.
  • Daily publishing of builds on cdimage.ubuntu.com
  • Best effort help from foundation and release team members on requested rebuilds and analysis of build failures.

Coordination with Ubuntu release

  • Optional inclusion in Ubuntu development milestone releases.
  • Inclusion of image in release manifest if:
    • has been made daily.
    • has been released and tested in at least one beta milestone.
  • If image is to be published as part of a release manifest:
    • Images published and available through lifecycle.
    • Inclusion in release announcement (pointers to flavor page)
    • Inclusion in release notes (flavor overview and known issues)
    • Use of the ISO tracker for coordinating community testing of images for milestone releases
  • Link to flavor as recognized derivative from Ubuntu site http://www.ubuntu.com/project/about-ubuntu/derivatives

  • Weekly meeting for sharing status and clarifying dependencies between teams.

Support post release

  • availability of security updates for packages in main that overlap with Ubuntu
  • availability of kernel updates that overlap with official Ubuntu kernel for a release (?new hardware support going forward)
  • image available in archive through lifecycle of release

Services that Canonical does not provide (but community members may)

  • testing of images on iso tracker.
  • fixing of packages not in the Ubuntu desktop or server images.
  • security updates of package not in main.
  • publishing on releases.ubuntu.com
  • mastering physical CDs and USB sticks.

Criteria to have an image added to the dailies

  • Official Flavor has been approved by Tech Board
  • All packages are publicly available in Launchpad Archive (Main or Universe)
  • Launchpad bug infrastructure is monitored and updated for tracking defects related to packages in an image.
  • IS has signed off that there is sufficient space to support image builds and publishing
  • Release team member lined up to work with team to debug adding it into servers.
  • Community member lined up to test image and provide feedback at milestones.

Criteria to become and remain a recognized flavor:

PROPOSAL: recommendations for Tech Board consideration for the criteria

  • Image has track record of community interested in creating, supporting and promoting its use.
  • Leading members have signed Ubuntu Code of Conduct.
  • One or more developer with upload rights.
  • Flavor lead identified and responsive though 6 month cycle.
  • Flavor QA lead identified to coordinate testing of image at milestones during release.
  • Follow the milestone and release processes.
  • Best effort support from flavor community for security updates and high priority bug fixes for default 18 month support period.
  • If flavor ceases to do active releases for consecutive cycles, release team may request the TechBoard review whether it should remain recognized flavor.

Criteria to designate flavor image as LTS

PROPOSAL: recommendations for Tech Board consideration for the criteria.

  • Align with Ubuntu LTS release cycle.
  • Flavor's support plan presented to Tech Board and approved; support plan should indicate period of time if beyond 18months (3yrs or 5yr), key contacts, and setting expectations as to level of support.
  • Support plan public and ongoing support contacts accessible for discussion of bugs and security issues (or alternates designated) through life of project.
  • Key Upstream packages worth supporting for extended cycle.
  • Written confirmation from IS that space and resources are available to retain images in archive through LTS life cycle.