coordination #91646
closed
[saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
Added by okurz about 3 years ago.
Updated 9 months ago.
Estimated time:
(Total: 0.00 h)
Description
Motivation¶
Scale up the business while ensuring highest quality with automated testing, approval and release of package updates for SLE and openSUSE
Related issues
1 (1 open — 0 closed)
- Project changed from 46 to QA
- Tracker changed from action to coordination
- Subject changed from [saga][epic] Improve SUSE Maintenance QA workflows with fully automated testing, approval and release to [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
- Target version changed from Ready to future
with #91605 put to future again, see #91605#note-4 , with the support of more internal stakeholders, with the need of focussing on existing sagas to get something done before we pick up more new stories, with the quick solutions applied as part of #91542 and #91467 we decide that currently for the foreseeable future of next weeks we will not continue work here and focus on other sagas instead, see https://progress.opensuse.org/issues?query_id=524
- Target version changed from future to Ready
- Copied to coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release added
Had a discussion with vpelcak about some topics:
- mawerner has stated again that "gut-feeling" is the base for product validation -> direct consequence is that maintenance tests will fail and nobody cares to fix them
- proposal to move more tests from aggregate to incident tests
- I think that the cost-benefit ratio investing effort in automatic classification #102915 is better than for #104209
- Status changed from Blocked to Resolved
All subtasks resolved. With this we call the whole saga resolved \o/
Also available in: Atom
PDF