= openSUSE release teams

Important teams external to direct release engineering

== Marketing

- Creating and following a marketing plan. The old plan focussed on
  new features while Leap is more about stability. Marketing content
  is usually found in the wiki.
- Taking care of social media
- Collecting statistics to measure success
- Creating a press release document

== Design

- Making sure all Desktops are consistently branded, Fonts are
  correct on all desktops, etc.
- Optional: Making sure look&feel of infrastructure related to the
  release is consistent.

== Infrastructure

Making sure criticial infrastructure works as designed and contains
the right data in the crucial phases:

- beans.o.o
- build.o.o
- countdown.o.o
- download.o.o
- mirroring system
- news.o.o
- shop.o.o
- software.o.o
- wiki
- www.o.o

== Documentation

- Keeping release notes, wiki articles, web site content etc related
  to the release up to date.

== Translations

- Communicating items to translate to language coordinators. Making
  sure important pieces are translated to the main languages.
- Coordinating translations between software translations and wiki
  (uses different processes and potentially different teams)

== QA

- Creating a test plan for each milestone and making sure crucial
  areas are covered.
- Monitoring bugzilla and escalating important regressions to the
  release manager
- Monitoring openQA and fixing issues caused by broken test cases or
  engine failures