action #20518
closed
Oliver, could you take care of this? GM is already tagged.
- Due date changed from 2017-07-28 to 2017-08-04
Sure, I can do this. I wonder about the job group. We added support for version-specific tags so that we can cover more than one version in one job group. I replaced your tag with tag:42.3-0331:important:GM so we can also rename the job group to just "openSUSE Leap" and add openSUSE Leap 15 there later. WDYT?
we talked about this on the release party. I don't really mind but don't see much value either. copying to a new job group can be scripted so not much of an issue.
- Status changed from New to In Progress
Ok, I moved the groups openSUSE Leap 42.3, openSUSE Leap 42.3 PowerPC, openSUSE Leap 42.3 AArch64 to the "old" parent group and reduced the quota a bit. A version-agnostic job group is an option for later, e.g. dot-releases of Leap 15 and potentially following ones when we don't have a backward moving version jump ;-P I will review "fixed" assets on o3.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF