[Fedora QA] #394: Revise validation process / templates for ARM as primary arch
by fedora-badges
#394: Revise validation process / templates for ARM as primary arch
----------------------+------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 20
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
ARM has been accepted as a primary arch at least for buildsystem purposes.
The plan is to have 'primary' ARM deliverables as well if possible. This
may require us to revise the validation process / template pages to
incorporate ARM testing. It may be as 'simple' as throwing a couple of
extra columns (for the two ARM variants) alongside x86_64, i686 and EFI in
the templates, but we will have to take a look.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/394>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #363: Require spins to go through smoke testing before being published
by fedora-badges
#363: Require spins to go through smoke testing before being published
-------------------------+----------------------------------
Reporter: adamwill | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Test cases | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+----------------------------------
= problem =
Sometimes, we publish spins that are completely DOA.
= analysis =
There is no mandatory testing of any Fedora images beyond netinst, DVD and
the two release blocking desktop live spins, as things stand, but we
publish rather more spins than that. In practice we test Xfce, LXDE, SoaS
and AMI images to some extent, but others are rarely touched.
= enhancement recommendation =
viking-ice has suggested that we should produce some kind of validation
matrix which has very basic, generic smoke tests: basically, does the
image at least boot up sanely? We would require there to be a PASS for
these mandatory smoke tests present in that matrix for a spin image to be
published on the spins page. QA does not commit to doing the actual
testing; we may do so if we have time, but ultimately, if a spin owner
wants to have their spin published, it's their responsibility to get the
testing done, either by poking QA, doing it themselves, or getting someone
else to do it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/363>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #336: ARM as primary arch
by fedora-badges
#336: ARM as primary arch
------------------------------+------------------------
Reporter: jdulaney | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 19
Component: Release criteria | Version:
Keywords: | Blocked By:
Blocking: |
------------------------------+------------------------
I'm opening this ticket to track integrating ARM into the current QA
process. Paul Whalen is my contact from the ARM side; at FUDCon I gave
him the 30,000' view of the current QA process.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/336>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #307: Add multi-desktop and multi-arch images to validation process
by fedora-badges
#307: Add multi-desktop and multi-arch images to validation process
----------------------------------------+------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: critical | Milestone: Fedora 18
Component: Blocker/NTH review process | Version:
Keywords: | Blocked By:
Blocking: |
----------------------------------------+------------------------
For the last few releases, we've been releasing two dual-layer DVD images
- one contains both the 32-bit and 64-bit DVD images, and the other
contains the major live spins all together with a menu for picking which
one to boot.
We don't really encourage public downloads of these, but we _do_ print
them on physical media and distribute them at conferences and via the
ambassadors program. Apparently, for F17, at least one of the images
turned out to be badly broken and we printed/gave out several thousand
coasters. Whoops. So, it seems we can't rely on these compendium images to
always be working properly, and QA should be validating them before
they're used for anything.
We'll need to co-ordinate with releng, FAmSCo and possibly FPL on this
one, for timing issues. The compendium images are built _after_ the main
set of final release images, and this is probably unavoidable, because we
have to sign off definitely on the release images before building
compilations of them. So we should probably define an official schedule
and process for building and testing the compendium images right after the
go/no-go, on a schedule that works for FAmSCo and regularly-scheduled
events where these media are distributed. CCing Robyn (FPL) and cwickert
for FAmSCo.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/307>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #297: Review release criteria for Fedora 18
by fedora-badges
#297: Review release criteria for Fedora 18
-----------------------------------------+------------------------
Reporter: adamwill | Owner: pschindl
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------------
Petr suggests on the F17 retrospective:
"We should reviewed release criteria, dismiss all which are obsolete and
maybe add some new (like we did for PXE). This step should be done in
cooperation with other teams (like anaconda and FESCo)."
This is kind of a follow-up to https://fedorahosted.org/fedora-
qa/ticket/151 .
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/297>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #277: Add ARM to release criteria / validation process somehow
by fedora-badges
#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
9 years, 2 months