https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-06-11T09:16:25ZopenSUSE Project Management ToolQA - coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incidenthttps://progress.opensuse.org/issues/93871?journal_id=4155852021-06-11T09:16:25Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Ready</i></li></ul><p>thank you. so do you plan to create subtickets for the individual tools that need changing? I think we just have to do it. But having tickets can at least explain to others why we don't do other stuff in the meantime :)</p>
QA - coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incidenthttps://progress.opensuse.org/issues/93871?journal_id=4155972021-06-11T09:19:15Zjbaier_czjbaier@suse.cz
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/80690">action #80690</a>: [qem] Testing of packages in different codestreams but in one incident</i> added</li></ul> QA - coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incidenthttps://progress.opensuse.org/issues/93871?journal_id=4162542021-06-15T08:37:14Zokurzokurz@suse.com
<ul><li><strong>Tracker</strong> changed from <i>action</i> to <i>coordination</i></li><li><strong>Subject</strong> changed from <i>Change in the maintenance requests - improve of the process to submit packages that belong together in one incident.</i> to <i>[epic] Change in the maintenance requests - improve of the process to submit packages that belong together in one incident.</i></li></ul> QA - coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incidenthttps://progress.opensuse.org/issues/93871?journal_id=4176432021-06-18T11:02:54Zhrommel1heiko.rommel@suse.com
<ul><li><strong>Subject</strong> changed from <i>[epic] Change in the maintenance requests - improve of the process to submit packages that belong together in one incident.</i> to <i>[epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incident</i></li></ul><p>I have updated the title to reflect the driving force behind this change.</p>
<p>The agreement with Maintenance Coordination and Security is that we want to work towards allowing packages from different code streams within a single incident as long as the fix set / features list is <u>identical</u>. Hence the resulting test plan would be very similar.</p>
<p>Apart from adaptions to be done on the tooling side, we might run into situations where we can not finish testing on all affected code streams/products in time. If that happens, the Maintenance Coordination or Security team might decide if to break down the incident into smaller pieces.</p>
QA - coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incidenthttps://progress.opensuse.org/issues/93871?journal_id=4249572021-07-09T08:21:20Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>osukup</i></del>)</li><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>We need to clarify what is needed and what can be done without relying on single individuals hence unassigning osukup and moving out of the current backlog</p>