Re: [Fedora QA] #2: Wiki cleanup
by fedora-badges
#2: Wiki cleanup
-----------------------+----------------------------------------------------
Reporter: johannbg | Owner: somebody
Type: task | Status: closed
Priority: major | Milestone:
Component: Wiki | Version:
Resolution: invalid | Keywords:
-----------------------+----------------------------------------------------
Changes (by adamwill):
* status: new => closed
* resolution: => invalid
Comment:
I think James was on the right track here and we should just close this
ticket. Tickets work best for tracking specific tasks which are documented
and then implemented and the ticket closed, not for an ongoing, broad
'conceptual' task.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/2#comment:8>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #196: proventester request
by fedora-badges
#196: proventester request
-----------------------------------------+----------------------------------
Reporter: azur3l1ght | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Hi , i would like to apply for proven testers team. I have 4 years as QA
in different projects and recently switched to Fedora .
Greetings
Georgi
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/196>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #145: Request to join ProvenTester
by fedora-badges
#145: Request to join ProvenTester
-----------------------------------------+----------------------------------
Reporter: dbhole | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
OpenJDK is a widely used package, and has quarterly security updates (at
the very least). While we (devel and qe) team test it, there is no way for
us to set a +1 karma as a proven-tester.
To that end, I would like to apply for proven tester status. In addition
to OpenJDK, this will also allow me to test and set the proper Karma for
other packages our team owns.
I'd be happy to follow and training guidelines laid out by a Proventester
Mentor.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/145>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #98: Request for a Mentor
by fedora-badges
#98: Request for a Mentor
-----------------------------------------+----------------------------------
Reporter: jdulaney | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
I would like to now formally request a Proven Tester Mentor. I have been
running Fedora since FC1, generally updating every other release (I
skipped 9 and went straight to 10). I have several boxes so as to get
different hardware involved.
Thanks,
John H. Dulaney
https://fedoraproject.org/wiki/User:Jdulaney
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/98>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #60: Devise a better location for critpath.txt
by fedora-badges
#60: Devise a better location for critpath.txt
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
critpath.txt lists critical path packages [1]. Currently it is referenced
as
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<CURRENT
DATE>>/logs/critpath.txt
}}}
or
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<YESTERDAY
DATE>>/logs/critpath.txt
}}}
depending on which page. Similarly for branched releases.
This is not optimal. Very often the url just doesn't work. For example at
the time of writing critpath.txt on F13 Alpha Release Criteria page [2]
references rawhide-20100407/ directory, where critpath.txt is not
available. Nor it is available in rawhide-20100406/ directory. Only in
rawhide-20100405/ it is finally available.
The very page Critical Path Packages [1] references critpath.txt for
Branched release, which is available ATM, but also references critpath.txt
for Rawhide, which is again not available.
Let's imagine other use case - some automated tool must decide whether
package in the critical path. It can't rely on path which are constantly
changing and sometimes are not available.
critpath.txt is created dynamically, so we probably must have the contents
created every day or so. But we should devise such mechanism that the
location is stable and the file is always available (if new contents fails
to create, the old contents is still available). That will also allow
third-party tools to rely on it.
[1] https://fedoraproject.org/wiki/Critical_Path_Packages [[BR]]
[2] https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/60>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
Re: [Fedora QA] #12: Announcment web page.
by fedora-badges
#12: Announcment web page.
--------------------------+-------------------------------------------------
Reporter: johannbg | Owner: johannbg
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Trac | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by adamwill):
the infra ticket has now been closed on the basis that RSS feeds of the
various announcement lists are available. I don't believe any have been
subscribed to Planet Fedora. Johann, what's your thoughts on moving
forward (or not) with this now? Thanks!
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/12#comment:3>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #236: No qa test for making sure that the boot.iso is hybridised
by fedora-badges
#236: No qa test for making sure that the boot.iso is hybridised
--------------------+-------------------------------------------------------
Reporter: ausil | Owner: adamw
Type: defect | Status: new
Priority: major | Milestone:
Component: Trac | Version:
Keywords: |
--------------------+-------------------------------------------------------
= bug description =
F-16 alpha shipped witha boot.iso that did not have isohybrid run on it,
this means you can not just dd it to a usb drive and boot it.
= bug analysis =
slipped though as there was no test case
= fix recommendation =
lorax has been fixed, but we should make sure we cover it in testing.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/236>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months