action #95338
open[qe-core] Why version specific job groups for "Maintenance - QR"?
0%
Description
Observation¶
#94714#note-7 shows a reminder message because there was no new build in Maintenance - QR - SLE15SP2 since nearly a month. In the meantime there is Maintenance - QR - SLE15SP3 with newer builds. I assume "QR - SLE15SP2" can be considered done so I moved the job group to "EOL". But why create a version-specific job group at all? I suggest to simplify the setup and just schedule all versions in the same job group which should reduce the work needed, e.g. also in the job templates needing less manual updating.
Updated by okurz over 2 years ago
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by tjyrinki_suse over 2 years ago
- Priority changed from High to Normal
- Start date deleted (
2021-07-11)
From our point of view it's cleaner to not have a mega job group yml file with all versions, but one focused on each version. There's a small possibility of extra QU for an older version, which is why the job groups are kept around for a longer period that seems useful at first glance, but in general there's not much manual updating done for an older version once the focus shifts to a newer one.
Updated by slo-gin over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 month ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.