#277: Add ARM to release criteria / validation process somehow
----------------------+------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: critical | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: arm | Blocked By:
Blocking: |
----------------------+------------------------
= phenomenon =
ARM is becoming increasingly important to releases. Currently we have no
kind of formal validation process for ARM images. Let's work with the ARM
group to improve this, so we can test whatever is most important to them.
= background analysis =
ARM deployment is significantly different from x86: the standard way to do
things is to provide a pre-built image to dump onto the system, not to
'install' via anaconda. So a lot of our test suite, which is based around
anaconda, may not be entirely appropriate to ARM. Similarly, the desktop
validation stuff isn't likely to be super-interesting to them, as desktop
isn't currently a priority for ARM and things at that high a level ought
to pretty much 'just work'. We should figure out with the ARM team what it
would be most useful to test, and how to work testing into their release
process.
= implementation recommendation =
We may need to write a few new tests, then I think we should design an
ARM-specific validation matrix, which may be much smaller than the main
ones. To start with we may also want to start separate ARM release
criteria pages, to codify the things which are most important to ARM
releases.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/277>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
