action #93931
closed
coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incident
[tools][qem] MTUI support multiple versions of package in incident
Added by osukup almost 3 years ago.
Updated almost 3 years ago.
Description
Acceptance criteria¶
- new Incidents can be created using multiple code branches
Suggestion¶
- Parse new
PackageVer from template
- compare correct version during update/downgrade step
- export command exports correct versions per refhost
- list_packages command with the correct version
- Blocked by action #93934: [tools][qem] template generator - multiple package version in incident added
- Target version set to Ready
@osukup how would you judge the urgency of this ticket? Strictly speaking, when do we need this?
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to osukup
@okurz - in an ideal state, before the first Incident with this change :(
-> It needs move package versions storage and handling from Testreport class to Target + optimally also 'add/remove repo' etc
- Due date set to 2021-07-03
Setting due date based on mean cycle time of SUSE QE Tools
- Has duplicate action #80690: [qem] Testing of packages in different codestreams but in one incident added
- Priority changed from Normal to Low
I understood from hrommel1 that this task would be good to follow-up and finish but is considered less important than for example #92125 as IIUC workarounds are known and the impact is limited to mtui. If possible please finish fast or unassign to be picked up later again.
okurz wrote:
as IIUC workarounds are known and the impact is limited to mtui
Maybe I miss something, but I am not really aware of any workaround. The impact is limited to testing incidents with this "feature" (and there are such in the queue at this moment).
- Description updated (diff)
- Status changed from In Progress to Feedback
if no complaint about devel version of MTUI +- on Monday create new versio n branch and publish in stable channel
- Status changed from Feedback to Resolved
- Due date deleted (
2021-07-03)
Also available in: Atom
PDF