Fedora install support for netbooks -- small screen size
by Robert Moskowitz
I am doing another FC12 install on my ASUS 701ee. This is a test
system, and I end up installing every month or so.
Of course with the small screen size, I end up pressing <cntl-N> a lot,
as I cannot see the Next button. And on some screens I just miss some
options, like getting to customize the install packages. I am always
forgetting the key combo to turn that check box on.
Is there some way to either get the ability to pan the screen around or
scroll the screen so that on Netbooks that SHOULD be a popular install
platform for Fedora, can have workable installation?
13 years, 3 months
[Fedora QA] #90: Make blocker bug nag mails part of the SOP
by fedora-badges
#90: Make blocker bug nag mails part of the SOP
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: poelstra
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
We have a lot of bugs, and the deadlines for resolving bugs (where
resolving == [fixing, documenting]) is not always clear.
= analysis =
During the lead up to F-13-RC, numerous reminder emails were sent to test@
and devel@ mailing lists noting the number and state of remaining blocker
bugs. It is felt that, along with developer time of course, the attention
to the blocker list contributed to the resolution of 67 blocker bugs from
2010-04-30 to 2010-05-06.
Not knowing which bugs were already reviewed, also introduced time wasted
reviewing previously reviewed bugs during blocker review meetings.
= enhancement recommendation =
1. Recommend more frequent blocker status emails leading up to '''each'''
major milestone. Unclear who should be responsible for sending these
mails, QA, rel-eng or program mgmt?
2. Update [https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
QA:SOP_Blocker_Bug_Meeting] with blocker meeting queries or ''python-
bugzilla'' commands and where to send the mails (developers bcc'd?)
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/90>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 5 months
[Fedora QA] #85: Clarify wiki test priority
by fedora-badges
#85: Clarify wiki test priority
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
There was some confusing around the priority listed in the install and
desktop test matrices. The question was, why do we give the ''go''
decision to release, even when there are test failures from tests with a
matching release level?
= analysis =
Adam pointed out that ''this is because the bugs exposed caused the test
to 'fail', but don't really break the underlying release criteria. I think
we could perhaps track this type of 'failure' specifically in the results
tables).''
= enhancement recommendation =
I ''think'' this is a messaging/education issue. Perhaps we just need to
clarify that the priority listed is the test execution priority. It does
not always mean that a failure identified by those tests will block the
applicable release.
Updates or adjustments may be needed to the
https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event or to
the Fedora 14 test results template (when available --
https://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/85>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 5 months
[Fedora QA] #114: Proposed Test Day - Virtualization
by fedora-badges
#114: Proposed Test Day - Virtualization
----------------------+-----------------------------------------------------
Reporter: jforbes | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
I will be more than happy to plan/host the test day.
Preferred times are 2010-09-23 or 2010-09-30 or any other available day
before between the alpha release and then.
There are only a couple of new features to be tested, but we need coverage
across the board for virtualization as there has been a good bit of
change.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/114>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 5 months
[Fedora QA] #109: Proventester Mentor Request (fcami)
by fedora-badges
#109: Proventester Mentor Request (fcami)
-----------------------------------------+----------------------------------
Reporter: fcami | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
I would like to request a mentor to become Proventester.
I have read http://fedoraproject.org/wiki/Proven_tester, I agree to abide
by the testing requirements and I know how to use bodhi and bugzilla. I do
triage from time to time (mainly xorg, especially xorg-x11-drv-ati and
mesa).
I already use updates-testing enabled for quite of bit of my packages,
including some in the critical path, on about five different workstations
and servers
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/109>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 5 months
[Fedora QA] #117: proventester request for petersen (aka juhp)
by fedora-badges
#117: proventester request for petersen (aka juhp)
-----------------------------------------+----------------------------------
Reporter: petersen | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Hi, I would like to join proventesters to help support
the Fedora QA testing of important/critical path package
updates.
So this is a request for a mentor. :)
Jens
--
Fedora and Red Hat i18n Engineering Team
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/117>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 5 months
[Fedora QA] #87: Expand desktop release criteria and validation
by fedora-badges
#87: Expand desktop release criteria and validation
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
[http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Desktop
test results] were often not available for non-GNOME desktops. This
leaves a large exposure come release day (for Alpha, Beta or Final).
= analysis =
The desktop release criteria are specific to GNOME. As a result, there is
no incentive to finding bugs in XFCE, LXDE or KDE.
= enhancement recommendation =
This might be too much for once ticket. Feel free to split this out into
more if needed.
Recommend looking for opportunities to improve communication between teams
and increasing non-GNOME desktop testing leading up to milestones.
* The goal is to extend the desktop validation testing introduced in
Fedora 13 to cover the main non-default desktops: KDE, Xfce and LXDE.
* Update appropriate desktop validation content as needed (see
[http://fedoraproject.org/wiki/QA:Desktop_validation_testing desktop
validation testing])
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/87>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
[Fedora QA] #94: Add several release criteria based on feedback from desktop SIGs
by fedora-badges
#94: Add several release criteria based on feedback from desktop SIGs
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 14
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Discussing the expansion of desktop validation testing to other major
desktops - https://fedorahosted.org/fedora-qa/ticket/87 - has resulted in
several proposed additional release criteria:
* Saving passwords in the desktop default keyring (if the desktop
implements one), and retrieving passwords from the keyring, must work
* The desktop default update manager must not periodically check for
updates when the system is booted live, but must periodically check for
updates when running on an installed system
* The desktop's offered mechanisms for shutting down, logging out and
rebooting must work
We should consider adding these to the release criteria, and select
appropriate levels for each.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/94>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
[Fedora QA] #105: F14 Graphics Test Week
by fedora-badges
#105: F14 Graphics Test Week
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
We should have a Graphics Test Week for F14, as usual. I will organize it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/105>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
