On Fri, Jun 18, 2010 at 5:27 PM, Aaron Faanes wrote:
> On Fri, Jun 18, 2010 at 2:14 PM, Adam Williamson wrote:
>> On Thu, 2010-06-17 at 23:05 -0500, Aaron Faanes wrote:
>>
>>> I worked on this draft a bit on my own user-page. Specifically, I
>>> wikified some of the links and heavily edited the o
The following builds have been pushed to Fedora 12 updates-testing
banshee-1.6.1-2.fc12
bdii-5.1.7-1.fc12
clamav-0.96.1-1200.fc12
crm114-0-1.12.20090807.fc12
font-manager-0.5.4-5.fc12
glue-schema-2.0.6-1.fc12
gnome-applet-timer-2.1.2-7.fc12
gyachi-1.2.9-2.fc12
h
The following builds have been pushed to Fedora 11 updates-testing
crm114-0-1.10.20080703.fc11
font-manager-0.5.4-5.fc11
glue-schema-2.0.6-1.fc11
gyachi-1.2.9-3.fc11
nautilus-pastebin-0.5.0-2.fc11
octave-forge-20090607-16.fc11
openttd-1.0.2-1.fc11
perl-HTTP-DAV-0.40
Dear Adam:
> Can anyone that knows what is going on behind the doors at
> FedoraProject, tell me if webkit2 will be available for fc14?
There aren't any 'doors', Fedora is an open project. There's no Grand
Central Planning that decides these things. I suggest you simply ask the
webkit maintainer
On Mon, 2010-06-21 at 18:31 +, "Jóhann B. Guðmundsson" wrote:
> On 06/21/2010 06:22 PM, TK009 wrote:
> > On Mon, 21 Jun 2010 13:44:47 -0400
> > James Laska wrote:
> >
> >> More food for thought ...
> >>
> >> I've heard thoughts from others about how the 'test day' name doesn't
> >> accurat
On 06/21/2010 06:22 PM, TK009 wrote:
> On Mon, 21 Jun 2010 13:44:47 -0400
> James Laska wrote:
>
>> More food for thought ...
>>
>> I've heard thoughts from others about how the 'test day' name doesn't
>> accurately match the effort. One suggestion was to rebrand the effort
>> as 'bug day'.
On Mon, 21 Jun 2010 13:44:47 -0400
James Laska wrote:
> More food for thought ...
>
> I've heard thoughts from others about how the 'test day' name doesn't
> accurately match the effort. One suggestion was to rebrand the effort
> as 'bug day'. Similar to http://live.gnome.org/Bugsquad/BugDays
>
On Mon, 2010-06-21 at 10:30 -0700, Adam Williamson wrote:
> On Mon, 2010-06-21 at 08:35 -0600, Eric Blake wrote:
> > On 06/18/2010 10:43 PM, Adam Williamson wrote:
> > >> 3. Calling it a Test _Day_ sure makes it sound like it is limited to a
> > >> single 24hour period. Maybe this is a marketing
On Mon, 2010-06-21 at 08:35 -0600, Eric Blake wrote:
> On 06/18/2010 10:43 PM, Adam Williamson wrote:
> >> 3. Calling it a Test _Day_ sure makes it sound like it is limited to a
> >> single 24hour period. Maybe this is a marketing problem, is there a
> >> better name?
> >
> > If there is, I hav
Josef Skladanka redhat.com> writes:
> * TCs/RCs archive (kparal, 15:52:50)
>* ACTION: robatino to ask infrastructure team to archive previous
> RCs/TCs (kparal, 15:57:23)
https://fedorahosted.org/fedora-infrastructure/ticket/2241
--
test mailing list
test@lists.fedoraproject.org
==
#fedora-meeting: Fedora QA Meeting
==
Meeting started by jlaska at 14:59:57 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-06-21/fedora-qa.2010-06-21-14.59.log.html
.
Meeting summary
--
#60: Devise a better location for critpath.txt
--+-
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major| Milestone:
Component: Wiki | Versi
On 06/18/2010 10:43 PM, Adam Williamson wrote:
>> 3. Calling it a Test _Day_ sure makes it sound like it is limited to a
>> single 24hour period. Maybe this is a marketing problem, is there a
>> better name?
>
> If there is, I haven't been able to think of it :(. As I said, the
> problem is it
# Fedora Quality Assurance Meeting
# Date: 2010-06-21
# Time: 15:00 UTC (11:00 EDT, 17:00 CEST) [1]
# Location: #fedora-meeting on irc.freenode.net
Greetings gang,
Just a quick check-in on current activities. See the proposed agenda
below. As always, corrections+suggestions to the agenda are w
The following builds have been pushed to Fedora 11 updates-testing
389-ds-base-1.2.6-0.7.rc2.fc11
cups-1.4.4-2.fc11
dhcp-4.1.0p1-6.fc11
Details about builds:
389-ds-base-1.2.6-0.7.rc2.fc11 (FEDORA-2010
- "He Rui" wrote:
> Then How about adding a step 4 in 'How to test' like:
> # Proceed and complete installation with VNC client.
> And in the 'Expected Results', add a step like:
> # VNC works normally during installation and anaconda can be
> configured
> by both mouse and keyboard.
Sure t
16 matches
Mail list logo