[yast-devel] Bugs Priority: Explanation
Hi, I've asked SLE 12 release managers to explain their understanding of priorities for SLE 12m this explanation comes from Thorsten Kukuk: --- cut --- P1: ship stopper for GMC, best all of them are fixed before RC1 P1s are also those bugs, that you cannot fix with a maintenance update P2: should be fixed best before GMC, but can be solved with a maintenance update, too P3: something which can wait for the next service pack P4: fix it if it is easy to fix and you have to touch the package anyway, ignore or reject otherwise P5: release manager had no time to prioritize or important info is missing --- cut --- What needs to be fixed in "the current beta/RC" is marked as "Blocker=yes". Hope this helps. Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (1)
-
Lukas Ocilka