[Fedora QA] #273: Improve browseability of validation matrix pages
by fedora-badges
#273: Improve browseability of validation matrix pages
-----------------------------------------+------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 17
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------------
= problem =
cwickert and sandro have told us they have trouble finding the validation
matrix pages when they need them.
= analysis =
we do have the pages logically named and categorized, but it's still not
that easy to, for e.g., see all the desktop result pages for a given
release at a glance.
= enhancement recommendation =
We could add more categories, for example "Fedora XX
{{desktop,base,install}} validation results" categories, and any others
that come to mind (suggestions please!) It would be nice to have 'next /
previous' links that would let you browse from Final RC4 back to Final RC3
back to Final RC2 back to Final RC1 back to Final TC2 back to Final TC1
back to Beta RC4 and so on, but I'm not sure if that's plausible to
implement automatically (it would be relatively easy to do manually when
creating the pages, though).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/273>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #228: SOPs for Everything
by fedora-badges
#228: SOPs for Everything
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
We should have...SOPs for Everything!
This is a meta-ticket with the aim of identifying, well, everything QA
does, and making sure they all have SOPs. For a start, I'm going to do a
survey of the QA calendar for a release, and check whether we have an SOP
for each task.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/228>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #447: Proposed Test Day - ARM
by fedora-badges
#447: Proposed Test Day - ARM
----------------------+--------------------------
Reporter: pwhalen | Owner: Paul Whalen
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+--------------------------
= phenomenon =
Proposed test day for ARM to occur between Alpha and Beta.
= implementation recommendation =
Testing to include all deliverables and target platforms (including
Allwinner sunxi ARM SoC support).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/447>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #429: temporary membership in sysadmin-qa for atodorov so that beaker trial can continue
by fedora-badges
#429: temporary membership in sysadmin-qa for atodorov so that beaker trial can
continue
-------------------------+------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: permissions | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------
= phenomenon =
Long story short, atodorov is helping with the beaker trial we're doing
and he needs shell access to the machine in order to complete his work.
Assuming that this trial is successful, access to the beaker system(s)
will be controlled with a separate FAS group but until that is set up,
sysadmin-qa membership is the only way to get the required access.
I don't expect the need for membership to last any more than a couple of
weeks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/429>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months