Actions
action #9160
closedclarify maintenance needs
Start date:
2015-10-06
Due date:
2015-11-04
% Done:
100%
Estimated time:
4.00 h
Description
we need clarify how maintenance for Leap is done, e.g how to make sure SLE updates are released for Leap
Updated by msmeissn over 9 years ago
What to do:
-
openSUSE specific packages - handle just like 13.x
-
SLES specific packages
- handle released SLE12 updates:
- write auto importer: go over SUSE:SLE-12*:Update, look for fresh updates of packages used in Leap, autocreate incidents from the sources.XXX and patchinfo.XXX.
- handle unreleased SLE12 updates?
- auto importer that fetches SUSE:Maintenance:XXX incidents affecting leap, create incidents on the outside.
- handle released SLE12 updates:
-
how to handle Leap bugfixes where SLE does not react or too slow?
-
how to handle submissions for SLE packages in Leap?
- autodecline and forward to bugzilla?
- merge to the SUSE:maintenance:xxxx queues ?
Updated by msmeissn over 9 years ago
openSUSE:Leap:42.1 00Meta lookup.yml
is the mapping data.
Updated by lnussel over 9 years ago
- % Done changed from 0 to 50
Metting done. Benni wants to write a summary for approval.
Updated by msmeissn over 9 years ago
(internal) https://etherpad.nue.suse.com/p/leap-maintenance-draft
mail sent to department leads to sign off on some political issue inside.
Updated by msmeissn over 9 years ago
we had various discussions with Olaf Kirch and Coolo on strategies of releasing SLE/LEAP packages.
Updated by lnussel over 9 years ago
- Status changed from New to Closed
- % Done changed from 50 to 100
Actions