On Fri, 2010-07-30 at 21:14 -0400, John Dulaney wrote:
> Why would we have to make it submit reports now? Unless the steps
> needed to
> implement this are very few, there are plenty of other things that
> have a higher
> priority right now, no?
The tools should always be capable of submitting re
On Fri, Jul 30, 2010 at 14:25:46 -0700,
John Poelstra wrote:
>
> 617115 :: ON_QA :: livecd-tools :: David Huff :: rawhide live spins
> showing black screen instead of syslinux boot menu ::
> https://bugzilla.redhat.com/show_bug.cgi?id=617115
Just in case David sees this, this should have bee
Hi, everyone. Just a heads-up to proven testers: now Fedora 14 has been
branched, the proven tester process is in effect for Fedora 14 packages.
Just like Fedora 13, critical path updates for Fedora 14 (even while
it's in development) will require +1 from a proven tester and +1 from
someone differe
Why would we have to make it submit reports now? Unless the steps needed to
implement this are very few, there are plenty of other things that have a higher
priority right now, no?
John Dulaney
> Subject: Release criteria proposal: automated bug checking tools functionality
> From: awill...@re
So, in the blocker meeting today we discussed having specific criteria
for the functionality of automated bug handling tools (currently, that
would be abrt and setroubleshoot, and I think KDE has its own tool
similar to abrt as well).
I'd like to propose the following two criteria:
* Automated bu
REMINDER: This list must be clear by Tuesday (2010-08-03) to compose the
Fedora 14 Alpha Release Candidate on Thursday (2010-08-05). If blocker
bugs remain open our chances of release on time decrease rapidly.
Here's the latest!
615443 :: NEW :: livecd-tools :: Bruno Wolff III :: booting live
The following builds have been pushed to Fedora 14 updates-testing
calibre-0.7.10-2.fc14
cifs-utils-4.6-1.fc14
compiz-0.8.6-3.fc14
googlecl-0.9.9-1.fc14
groff-1.20.1-2.fc14
ikiwiki-3.20100722-1.fc14
ldc-0.9.2-9.20100609hg1653.fc14
libass-0.9.9-1.fc14
libmemcache
#112: 'Translation/Keyboard in anaconda' Test Day - 2010/09/09
---+
Reporter: rhe | Owner: rhe
Type: task | Status: new
Priority: major | Milestone: Fedora 14
Component:
On Fri, Jul 30, 2010 at 10:32 PM, Michael Cronenworth wrote:
> On 07/29/2010 04:01 PM, Adam Williamson wrote:
>> A bug in PackageKit got out in a Fedora 13 update
>> which broke update notification, which is obviously a big problem.
>> PackageKit isn't actually on the critical path for F13, but i
On 07/29/2010 04:01 PM, Adam Williamson wrote:
> A bug in PackageKit got out in a Fedora 13 update
> which broke update notification, which is obviously a big problem.
> PackageKit isn't actually on the critical path for F13, but it is for
> F14 and up.
Is there a big tracking this? Was it discu
On Fri, 2010-07-30 at 10:34 -0400, Bob Lightfoot wrote:
> Dear Team:
> Just a suggestion from a busy proventester. When using
> fedora-easy-karma it nicely provides links to the bodhi package page and
> most bug reports related to the update. For packages which have special
> testing req
As I've only done it once before on F13.
Is there a wiki, to go from F13 to F14-Branched,
F14-Rawhide to stay with Rawhide
Will it take a few days to trickle down?
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https:
Either that, or include a recomended procedure with package discription?
Easily automatable, me thinks.
John Dulaney, great grandson of Arthur Sr.
> Date: Fri, 30 Jul 2010 10:34:40 -0400
> From: boblf...@gmail.com
> To: test@lists.fedoraproject.org
> Subject: Re: Proven tester special testing
Dear Team:
Just a suggestion from a busy proventester. When using
fedora-easy-karma it nicely provides links to the bodhi package page and
most bug reports related to the update. For packages which have special
testing requirements {kernels and PackageKit} can the link to the
testing
Jeff Raber said the following on 07/29/2010 08:53 PM Pacific Time:
> On 07/22/2010 12:07 PM, John Poelstra wrote:
>> As announced last week on the development list, all Fedora bugs with a
>> version of "rawhide" (with some exceptions) will be rebased to version
>> "14" on the Fedora 14 branching da
On 07/30/2010 02:31 AM, Adam Williamson wrote:
> We've talked about special proven testers testing procedures for
> kernels, and now another candidate for special test procedures has
> emerged: PackageKit. A bug in PackageKit got out in a Fedora 13 update
> which broke update notification, which i
The following builds have been pushed to Fedora 12 updates-testing
atlas-3.8.3-14.fc12
dovecot-1.2.13-1.fc12
fedora-packager-0.5.1.0-1.fc12
gstreamer-java-1.4-2.fc12
gyachi-1.2.10-2.fc12
hplip-3.10.6-1.fc12
ibus-m17n-1.3.0-3.fc12
libyahoo2-1.0.1-1.fc12
paps-0.6.
The following builds have been pushed to Fedora 13 updates-testing
NetworkManager-openvpn-0.8.1-1.fc13
NetworkManager-pptp-0.8.1-1.fc13
atlas-3.8.3-16.fc13
dovecot-1.2.13-1.fc13
fedora-packager-0.5.1.0-1.fc13
fldigi-3.20.20-2.fc13
gstreamer-java-1.4-2.fc13
gyachi-1.
On Thu, 29 Jul 2010 17:13:50 -0400
"James Cassell" wrote:
> On Thu, 29 Jul 2010 17:01:36 -0400, Adam Williamson
> wrote:
>
> > As well as testing package installation,
> > we should test update notification and installation for such updates. We
> > can consider different ways of doing this, b
#83: Clarify installer test coverage with i18n team
--+-
Reporter: jlaska | Owner: rhe
Type: enhancement | Status: closed
Priority: major| Milestone: Fedora 14
C
#95: Create installation test results template and test plan for F-14
+---
Reporter: rhe| Owner: rhe
Type: task | Status: closed
Priority: major | Milestone: Fedora 14
Component: W
21 matches
Mail list logo
