User:AndreasStieger/Maintenance activities

Jump to: navigation, search

draft...

This documents attempts to define generic roles and activities that need to be done for openSUSE maintenance.

Role: Update manager for openSUSE Maintenance

  • check incoming maintenance submissions
  • supersede duplicated submissions
  • reject submissions that do not meet the maintenance policy, try to resolve
  • defer submissions for SLE inherited packages to SLE maintainer
  • merge submissions that go together
  • accept submissions and write patchinfo
  • augment incidents with packages that need to be re-built or are simply missing
  • resolve build failures and disable non-primary architectures that fail
  • Lock incidents
  • Re-open qam-openqa rejected incidents and escalate to developer
  • Accept release request in "new" state

2-3, proposed: everyone + security team for security incidents

Role: OpenQA manager for openSUSE Maintenance

  • review all test failures
  • trigger random failures again
  • Problem with update: reject qam-openqa review on the release request
  • Problem with tests: check OpenQA git and escalate to OpenQA team or fix

1, proposed: Martin

Role: Reviewer for openSUSE Maintenance

Role: SLES liaison manager with openSUSE Maintenance

  • fix incompletely imported incidents
  • when requested import complex incidents from SLE to openSUSE maintenance
  • maintain 00Meta
  • switch packages from/to SLE inherited if warranted by openSUSE maintenance policy
  • report openSUSE regressions to SLE maintenance
  • send openSUSE specific fixes to SLE maintenance

1, proposed: Andreas

Special and irregular activities

  • Configure repositories for the next release
  • test updates for a development release
  • discontinuing releases