Greetings folks,
It's been quiet on the test day front for some time now. However, rest
assured, we are kicking off the Fedora 13 test day schedule in style. I
invite you to join #fedora-test-day this Thursday, February 4, 2010 for
the first of many Fedora 13 test days.
Qian Cai and Steve Dicks
On Thu, 2010-08-05 at 13:08 -0400, Tom "spot" Callaway wrote:
> On 08/05/2010 12:59 PM, John Poelstra wrote:
> > 597858 [NEW - high - dwa...@redhat.com - --- -] "SELinux is preventing
> > firefox from making its memory writable and executable." crashes rawhide
> > firefox start
>
> The update to
On Thu, 2010-08-05 at 20:35 -0700, John Poelstra wrote:
> Meeting at our regular time and location!
>
> When: 16:00 UTC (12 PM EST/9 AM PST)
> Where: irc.freenode.net #fedora-bugzappers
>
> Please join us. Here are the bugs we'll look at and discuss:
>
> 621102 :: NEW :: udev :: Harald Hoyer ::
On Fri, 2010-08-06 at 10:57 -0400, Tom "spot" Callaway wrote:
> On 08/06/2010 10:16 AM, James Laska wrote:
> > 620211 :: NEW :: python-psyco :: kon...@tylerc.org :: python-psyco needs
> > porting to python 2.7 in F14 and devel ::
> > https://bugzilla.redhat.com/s
> When: Friday, 2010-08-27 @ 16:00 UTC (12 PM EST)
> Where: #fedora-bugzappers on irc.freenode.net
Right of the coat tails of Fedora 14 Alpha, it's time for another
installment of the blocker bug review meeting! Friday kicks
off the first of several Beta bug review meetings.
If you are the owne
#fedora-bugzappers: F-14-Beta blocker review
Meeting started by jlaska at 16:00:10 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-27/f-14-beta-blocker-review.2
On Tue, 2010-09-14 at 16:01 -0600, Kevin Fenzi wrote:
> * #461 F14 blessing for systemd (nirik, 20:12:29)
> * LINK:
> http://fedoraproject.org/wiki/QA:Testcase_initialization_basic
> and http://fedoraproject.org/wiki/QA:Testcase_initialization_tools
> (nirik, 20:38:06)
> * ACTION: : wi
On Wed, 2010-09-15 at 09:32 -0700, John Poelstra wrote:
> The Fedora 14 Beta RC compose is scheduled for tomorrow.
>
> ALL open bugs on Fedora 14 Blocker list (http://bit.ly/cZKo9K) MUST
> BE
> FIXED TODAY or we risk delaying the release. In other words we are
> very
> short on time to address
Greetings folks,
This has been announced in several other forums already, but we missed
test-annou...@l.fp.org. See below for additional details and
information on how to participate.
Hope to see you in #fedora-test-day!
Thanks,
James
On Wed, 2010-09-22 at 15:35 -0500, Justin M. Forbes wrote:
On Thu, 2010-09-23 at 12:58 +0100, Adam Williamson wrote:
> Hi, everyone. So we partly used the proposed new nice-to-have bug
> tracking system during the F14 Beta process, and it seemed to go well.
> In a quick burst of airport productivity, I've quickly written up a
> bunch of proposed new wiki p
On Wed, 2010-09-29 at 09:55 +0100, Richard W.M. Jones wrote:
> If you've been following updates to F14 alpha/beta, you'll undoubtedly
> have been hit by:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=638091
>
> which makes everything segfault and is unrecoverable without a live CD
> and a lot o
Greetings,
This is great data, thanks for sharing Orion! I've cc'd the test@ list
as well since I think this is of value there.
On Wed, 2010-09-29 at 11:10 -0600, Orion Poplawski wrote:
> I apologize for this little bit of hubris. I recently filed my 1000th bug
> report at bugzilla.redhat.co
On Fri, 2010-10-01 at 12:36 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Again, you're extrapolating way too far from a single problem case. The
> > problem is simply that we have the xorg-x11-drivers metapackage which
> > requires every single X driver and is in the critpath. There's va
==
#fedora-bugzappers: F14 Blocker Bug Review
==
Meeting started by jlaska at 16:00:07 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-10-01/f-14-blocker-review.2010-10-01-1
On Wed, 2010-10-06 at 12:32 -0700, Adam Williamson wrote:
> On Wed, 2010-10-06 at 14:58 -0400, John Poelstra wrote:
> > Adam Williamson said the following on 10/06/2010 01:32 PM Pacific Time:
> > > On Thu, 2010-09-23 at 12:58 +0100, Adam Williamson wrote:
> > >> Hi, everyone. So we partly used the
On Fri, 2010-10-08 at 07:12 -0400, John Poelstra wrote:
> Adam Williamson said the following on 10/07/2010 01:24 PM Pacific Time:
> >>> https://fedoraproject.org/wiki/User:Adamwill/QA:SOP_nth_process_nth_draft
> >>> is a proposed new page which covers the whole nice-to-have review process
> >>> m
On Fri, 2010-10-08 at 11:33 -0400, John Dulaney wrote:
> All,
>
> I shall be working on some web frontends for ResultsDB, and I have
> been told that y'all already have some mock-ups/ideas for such a
> beast. If so, could y'all point me in the right direction.
I think this was intended for autoq
=
#fedora-bugzappers: Fedora 14 Blocker Bug Review
https://bugzilla.redhat.com/showdependencytree.cgi?id=538277&hide_resolved=1
===
On Fri, 2010-10-08 at 12:42 -0700, Adam Williamson wrote:
> On Fri, 2010-10-08 at 11:23 -0400, James Laska wrote:
>
> > > Would it be overkill to put more explicit testing sign-off around NTH
> > > bugs?
> >
> > I don't see why not. I think this
On Mon, 2010-10-11 at 13:16 -0400, Bill Nottingham wrote:
> Matthias Clasen (mcla...@redhat.com) said:
> > That is certainly a big part of the problem. Anaconda does a _ton_ of
> > crap that only very few users care about. And keeping all these minority
> > features from falling apart is leaving y
Greetings testers!
The bugs listed below are Fedora 14 Blocker bugs that are believed to be
fixed. Help is needed to ensure Fedora 14 ships on time! You can
follow the list of ON_QA bugs at http://bit.ly/bLdmof
To get started, for each bug ...
1. Confirm reported bug is fixed, then change
Greetings folks,
I'd like to draw attention to the QA retrospective wiki page for Fedora
14.
https://fedoraproject.org/wiki/Fedora_14_QA_Retrospective
As we did for Fedora 13 [1], I'd like to document any
gotchas/hiccups/awesome issues as they happen during a release. I don't
know about you, bu
On Mon, 2010-10-11 at 15:42 -0400, Bill Nottingham wrote:
> 1) When you added this to F14/F15/EL6, you added a typo; this
> broke the F-14 branched compose and the EPEL updates push.
> *Please* verify your changes before pushing.
How did the compose break? Is this something that the autoqa
rats_
On Tue, 2010-10-12 at 16:54 -0400, Bill Nottingham wrote:
> James Laska (jla...@redhat.com) said:
> > > 1) When you added this to F14/F15/EL6, you added a typo; this
> > > broke the F-14 branched compose and the EPEL updates push.
> > > *Please* verify your changes
On Tue, 2010-10-12 at 17:01 -0400, Bill Nottingham wrote:
> James Laska (jla...@redhat.com) said:
> > > No, this is well before the tree gets to that state. It would need to
> > > be implemented as a check on git push.
> >
> > We attempt to validate comps in thi
==
#fedora-bugzappers: Fedora 14 Final Blocker Review
==
Meeting started by poelcat at 16:00:21 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-10-15/fedora-
#fedora-bugzappers: F-14-Final Blocker Review Meeting -
https://bugzilla.redhat.com/showdependencytree.cgi?id=F14Blocker&hide_resolved=1
=
===
#fedora-bugzappers: Fedora 14 Final Blocker Review http://bit.ly/aBqOcu
===
Meeting started by poelcat at 16:01:15 UTC. The full logs are available
at
http:/
# F16 Alpha Blocker Review meeting #1
# Date: 2011-07-15
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Hard to believe, but the "vacation" is over. Fedora 16 Alpha test
compose is a few weeks away (Jul 26) and the Alpha is about a month
- Original Message -
> # F16 Alpha Blocker Review meeting #1
> # Date: 2011-07-15
> # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
> # Location: #fedora-bugzappers on irc.freenode.net
Just a reminder that the first Fedora 16 Alpha blocker bug review meeting
starts in under 1 hour
#fedora-bugzappers: F16-Alpha Blocker Review
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-15/f16-alpha-blocker.2011-07-15-17.00.html
Minutes (text):
http://meetbot.fedoraprojec
# F16 Alpha Blocker Review meeting #2
# Date: 2011-07-22
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
!!! ALL-CAPS RED-ALERT OMG LOL !!!
Fedora 16 Alpha test compose is less than *one* week away (Jul 26) and
F16 Alpha isn't far behind
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-22/f16-blocker-review.2011-07-22-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-22/f16-blocker-review.2011-07-22-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-22/f1
On Tue, 2011-07-26 at 13:03 +0100, Richard W.M. Jones wrote:
> On Tue, Jul 26, 2011 at 12:54:24PM +0100, Richard W.M. Jones wrote:
> >
> > newRepo seems to fail, although it's not clear why.
> >
> > http://koji.fedoraproject.org/koji/taskinfo?taskID=3230556
> >
> > Maybe something to do with bra
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-29/f16-alpha-blocker-review.2011-07-29-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-29/f16-alpha-blocker-review.2011-07-29-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2
# F16 Alpha Blocker Review meeting #4
# Date: 2011-08-05
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Mark your calendars ... the fourth Alpha blocker review meeting starts
at 17:00 UTC in #fedora-bugzappers this Friday. We'll review p
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-08-05/f16-blocker-review.2011-08-05-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-08-05/f16-blocker-review.2011-08-05-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-08-05
Greetings,
I have two packages proposed for review. Both are fairly small sized
python libraries. These packages are dependencies of autotest (which
should resurface for review soon-ish).
python-signalfd - https://bugzilla.redhat.com/show_bug.cgi?id=732737
python-atfork - https://bugzilla.red
# F15-Beta Blocker Review meeting #3
# Date: 2011-03-25
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Greetings!
The third Beta blocker review meeting will be this Friday at 17:00 UTC
in #fedora-bugzappers. We'll spend time reviewing p
# F15-Beta Blocker Review meeting #3
# Date: 2011-03-25
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Greetings,
This Friday is April 1st. I was trying to cook up something clever for
the blocker meeting, without causing too much heart
# F15-Beta Blocker Review meeting #5
# Date: 2011-04-08
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Mark your calendars, the fifth (and hopefully last) Beta blocker review
meeting will be this Friday at 17:00 UTC in #fedora-bugzappers.
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-08/f-15-beta-blocker-review.2011-04-08-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-08/f-15-beta-blocker-review.2011-04-08-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2
# F15 Blocker Review meeting #1
# Date: 2011-04-14
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Mark your calendars, the first F15 Final blocker review meeting will be
this Friday at 17:00 UTC in #fedora-bugzappers. We'll review propos
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-15/f-15-blocker-review.2011-04-15-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-15/f-15-blocker-review.2011-04-15-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-b
On Tue, 2011-04-19 at 11:05 +0200, Michael Schwendt wrote:
> On Tue, 19 Apr 2011 11:30:44 +0300, AT wrote:
>
> > > AutoQA is still in testing phase, there is no enforcement yet.
> >
> > Maybe the bodhi messages confused me. When I logon to a.f.o/updates it
> > prominently displays:
> >
> >
# F15 Blocker Review meeting #2
# Date: 2011-04-21
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
Due to upcoming holidays, the second F15 Final blocker review meeting
will be this Thursday at 17:00 UTC in #fedora-bugzappers. We'll revie
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-21/f15-blocker-review.2011-04-21-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-21/f15-blocker-review.2011-04-21-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-21/f1
On Wed, 2011-04-27 at 21:03 +0200, Tim Niemueller wrote:
> On 27.04.2011 15:38, Kamil Paral wrote:
> >>
> >> - Post only errors It is common, for example, in automated build or
> >> continuous integration systems to send out emails only on errors.
> >> Similar goes for Unix tools, which tend to be
# F15 Blocker Review meeting #2
# Date: 2011-04-29
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
The third (of four) F15 Final blocker review meetings will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll review proposed and
acc
=
#fedora-bugzappers: F15 blocker review #3
=
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-29/f15-blocker-review.2011-04-29-17.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugz
# F15 Blocker Review meeting #4
# Date: 2011-05-06
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
The *last* scheduled F15 Final blocker review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll review proposed and
acc
On Thu, 2011-05-12 at 22:24 -0600, Philip A. Prindeville wrote:
> On 05/12/2011 11:49 AM, Philip A. Prindeville wrote:
> > On 05/12/2011 09:01 AM, Nathanael D. Noblet wrote:
> >> On 05/12/2011 12:20 AM, Philip A. Prindeville wrote:
> >>> I'm seeing the following after trying to update an fc14.x86_6
Greetings testers,
Fedora 13 Alpha TC#2 is available for testing. Several test blocking
bugs present in TC#1 have been resolved. Please continue exercising the
Installation [1] and Desktop validation [2] to ensure that they meet the
Alpha Release Criteria [3].
All are welcome and encouraged to
=
#fedora-meeting: F-13-Alpha engineering readiness meeting
=
Meeting started by jlaska at 18:59:18 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2
Greetings,
The scheduled March 4 test day, with a focus on SSSDbyDefault [1], has
been postponed for a later date. Several planned changes to simplify
the user interface of authconfig-gtk were not completed in time for the
test day. The event will be reschedule for a later date.
Apologies for
Greetings,
Representatives from Fedora QA, Rel-Eng and Development met on IRC to
review determine whether the Fedora 13 Alpha release criteria [1] have
been met. The team agreed that the Alpha criteria have been met, and to
proceed with releasing F-13-Alpha-RC4. For additional details, please
re
On Thu, 2010-03-04 at 10:47 -0800, Adam Williamson wrote:
> On Thu, 2010-03-04 at 14:17 +0100, Kevin Kofler wrote:
> > James Laska wrote:
> > > Representatives from Fedora QA, Rel-Eng and Development met on IRC to
> > > review determine whether the Fedora 13 Alph
On Thu, 2010-03-04 at 21:06 +0100, Kevin Kofler wrote:
> Adam Williamson wrote:
> > I did explicitly explain to you and the other desktop SIGs at the start
> > of the F13 cycle that, because we just hadn't had time to discuss all
> > the thorny implications of the question, the desktop criteria wou
On Tue, 2010-03-09 at 13:41 -0500, Seth Vidal wrote:
>
> On Tue, 9 Mar 2010, Michael Schwendt wrote:
>
> > If you - and the QA team - want to expand your testing activities, focus
> > on the CRITPATH packages first. Do a good job there. Nobody from QA has
> > ever given feedback to any of my upda
On Wed, 2010-03-10 at 00:52 +0530, Rahul Sundaram wrote:
> Hi,
>
> Since it is the fav season for proposals apparently, let me throw in my
> Fedora/hat in the ring too. This only applies to updates to general
> releases.
>
> For critical path packages
> (http://fedoraproject.org/wiki/Critical_Pat
On Tue, 2010-03-09 at 19:50 +0100, Kevin Kofler wrote:
> Adam Williamson wrote:
> > The proposal isn't really about expanding testing activities, it's about
> > formally codifying how the updates process is actually supposed to work.
> > Right now, we don't in fact define how the Fedora update proc
On Tue, 2010-03-09 at 17:18 -0800, Adam Williamson wrote:
> On Tue, 2010-03-09 at 17:13 -0700, Kevin Fenzi wrote:
>
> > > Some basics I'd propose as a starting point for defining acceptance
> > > criteria include:
> > >
> > > 1. repoclosure/conflicts - no package update can introduce broken
On Wed, 2010-03-10 at 13:18 +, Paul Howarth wrote:
> On 09/03/10 20:43, James Laska wrote:
> > Some basics I'd propose as a starting point for defining acceptance
> > criteria include:
> >
> > 1. repoclosure/conflicts - no package update can intro
On Wed, 2010-03-10 at 11:13 -0600, Bruno Wolff III wrote:
> On Tue, Mar 09, 2010 at 15:43:04 -0500,
> James Laska wrote:
> >
> > 1. repoclosure/conflicts - no package update can introduce broken
> > deps or conflicts. I'd recommend we apply this
Greetings,
The first scheduled [1] Fedora 13 Beta blocker bug review was held
earlier today. In addition to evaluating the current list of F13Beta
bugs [2], we also reviewed the F13Blocker list [3] for bugs that fit the
Beta release criteria [4].
Thanks to all who helped move the meeting along.
Greetings,
The second scheduled [1] Fedora 13 Beta blocker bug review [2] was held
last Friday. The F13Beta blocker list [3] was reviewed and each bug was
evaluated against the beta release criteria [4].
Thanks to all who helped move the meeting along. A meeting recap is
attached and available
Greetings,
The Fedora 13 Beta 'release candidate' compose is scheduled [1] for this
Thursday (Mar 25, 2010). While testing is underway [2] against the Beta
'test compose' milestone, I wanted to remind folks that there are still
OPEN bugs on the F13Beta list [3] that impact the Beta release criter
On Tue, 2010-03-23 at 14:32 -0400, Cole Robinson wrote:
> On 03/23/2010 12:17 PM, James Laska wrote:
> > Greetings,
> >
> > The Fedora 13 Beta 'release candidate' compose is scheduled [1] for this
> > Thursday (Mar 25, 2010). While testing is underway [
Greetings,
As Fedora 13 marches towards a Beta, there are several Test Days planned
to help bring focused testing on upcoming features. The first,
scheduled for this Tuesday, March 30 2010, will focus on enabling SSSD
by default [1].
For those unfamiliar with SSSD, it's primary function is to pr
# F-13-Beta Go/No-Go meeting
# Date: 2010-04-01
# Time: 00:00 UTC (20:00 EDT, 17:00 PDT)
# Location: #fedora-meeting on irc.freenode.net
Before each public release Development, QA, and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is
Greetings,
Fedora 13 Beta RC#3 is available for testing. Release candidate #3
includes a fix for F13Beta blocker bug#578391. Please refer to the
summary sent earlier by Hurry for test focus areas [1]. If you are
interested in providing feedback against the Beta release criteria [2],
please cont
Greetings,
Representatives from Fedora QA, Rel-Eng and Development met on IRC to
review whether the Fedora 13 Beta release criteria [1] have been met.
The team agreed that the Beta criteria have not been met, and to slip in
the F-13 schedule by one week. For additional details, please refer to
th
Greetings,
Fedora 13 Beta RC#5 is available for testing. Beta RC#5 includes an
updated kernel to address F13Beta blocker bug#577463. Comparisons
against RC#4 are available (i386 [1] and x86_64 [2]). Once again,
thanks to Andre for creating the test results page and providing Delta
ISO's.
There
# F-13-Beta Go/No-Go meeting
# Date: 2010-04-08
# Time: 00:00 UTC (tonight @ 20:00 EDT, 17:00 PDT)
# Location: #fedora-meeting on irc.freenode.net
Before each public release Development, QA, and Release Engineering meet
to determine if the release criteria are met for a particular release.
This m
Greetings,
Representatives from Fedora QA, Rel-Eng and Development met on IRC to
review whether the Fedora 13 Beta release criteria [1] have been met.
The team agreed that the Beta criteria *have* been met with
F-13-Beta-RC5. For additional details, please refer to the attached
minutes.
Thanks,
On Thu, 2010-04-08 at 11:30 +0100, Mat Booth wrote:
> On 8 April 2010 01:33, James Laska wrote:
> > Greetings,
> >
> > Representatives from Fedora QA, Rel-Eng and Development met on IRC to
> > review whether the Fedora 13 Beta release criteria [1] have been met.
> &
Greetings folks,
Thanks to all those who attended and contributed testing during the SSSD
by default test day. We didn't anticipate a huge number of
participants, but given the revised authconfig user-interface, and that
SSSD will be used by default, we hoped for a larger turnout. If you
weren't
Greetings folks,
Is anyone interested in sponsoring a new package used in several
upcoming AutoQA test cases? The package is beakerlib (a shell-level
integration testing library), and the review request can be found at
https://bugzilla.redhat.com/show_bug.cgi?id=561470.
I've done my best to he
On Tue, 2010-04-13 at 12:55 -0500, Jason L Tibbitts III wrote:
> > "AW" == Adam Williamson writes:
>
> AW> I think it was just a thinko for 'review'.
>
> In which case, why would a sponsor be required at all? James is in the
> packager group, so he could just do the review. According to th
On Tue, 2010-04-13 at 13:58 -0500, Jason L Tibbitts III wrote:
> >>>>> "JL" == James Laska writes:
>
> JL> I take it from your response that you're not interested in reviewing
> JL> and sponsoring this package review request?
>
> Again, we
# What: F-13 Blocker bug review
# When: Friday, 2010-04-16 @ 15:00 UTC (11 AM EDT)
# Where: #fedora-bugzappers on irc.freenode.net
As if we needed another reminder that time flies, tomorrow will be the
first of 4 scheduled [1] Fedora 13 Blocker bug review meetings. We'll
be reviewing all F13Block
Greetings,
Not quite the blocker marathon from F-12, but 4 1/2 hours is a long time
to review blocker bugs. Thanks to all those who helped manage the list
ahead of time, or during the meeting.
Meeting minutes are attached and available for reference at
http://meetbot.fedoraproject.org/fedora-bug
# What: F-13 Blocker bug review
# When: Friday, 2010-04-30 @ 16:00 UTC (12 PM EDT)
# Where: #fedora-bugzappers on irc.freenode.net
Today will be the third scheduled [1] Fedora 13 Blocker bug review
meeting. We'll be reviewing all F13Blocker bugs [2] to determine
whether they impact the release cr
=
#fedora-bugzappers: F13Blocker Review
=
Meeting started by jlaska at 16:00:03 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-04-30/f-13-blocker-review.2010-04-30-16.00.log.html
.
Greetings,
I'm in the process of updating the existing mediawiki-semantic package.
The new version of mediawiki-semantic adds a dependency on an unpackaged
extension: Validator. Anyone interested in a review swap?
https://bugzilla.redhat.com/show_bug.cgi?id=784008
Thanks,
James
signature.asc
On Mon, 2012-01-23 at 11:34 -0500, Neil Horman wrote:
> On Mon, Jan 23, 2012 at 11:11:17AM -0500, James Laska wrote:
> > Greetings,
> >
> > I'm in the process of updating the existing mediawiki-semantic package.
> > The new version of mediawiki-semantic ad
On Thu, 2010-12-09 at 10:51 -0500, Adam Jackson wrote:
> 3) Reporting to bugzilla is a mistake.
Not discounting the idea, but just looking for more detail. What
alternatives would you want to see? More kerneloops-like aggregate data
collection, or something else?
Thanks,
James
signature.asc
D
Thanks Adam for getting the ball rolling on this topic.
On Tue, 2010-12-21 at 17:11 +, Adam Williamson wrote:
> Hi, everyone. So, in the recent debate about the update process it again
> became clear that we were lacking a good process for providing
> package-specific test instructions, and p
On Tue, 2010-12-21 at 15:53 -0700, Kevin Fenzi wrote:
> On Tue, 21 Dec 2010 17:11:15 +
> Adam Williamson wrote:
>
> > Hi, everyone. So, in the recent debate about the update process it
> > again became clear that we were lacking a good process for providing
> > package-specific test instructi
On Wed, 2010-12-22 at 17:29 +, Adam Williamson wrote:
> On Tue, 2010-12-21 at 18:12 -0500, James Laska wrote:
>
> > > the first isn't particularly specific to this, but it was a prerequisite
> > > that I discovered was missing: it's a guide to test case cre
On Thu, 2010-12-23 at 14:35 +, Adam Williamson wrote:
> On Tue, 2010-12-21 at 17:11 +, Adam Williamson wrote:
> > Hi, everyone. So, in the recent debate about the update process it again
> > became clear that we were lacking a good process for providing
> > package-specific test instruction
On Tue, 2011-01-04 at 17:57 +, Adam Williamson wrote:
> On Mon, 2011-01-03 at 10:52 -0500, James Laska wrote:
>
> > Agreed ... I think it makes sense to keep Category:Test_Cases as just a
> > container for sub-categories if possible. Mainly for the reasons you
> >
On Mon, 2011-01-24 at 16:52 +0100, Kevin Kofler wrote:
> Simo Sorce wrote:
> > We can easily test for rpath,
>
> But who does it on all packages regularly? AutoQA is still vaporware.
Because you haven't taken the time to familiarize yourself with a
project doesn't make it vaporware. AutoQA [1] w
Greetings,
On January 27, 2011, Fedora QA hosted a biosdevname Test Day [1].
Thanks to all who participated on wiki+irc, and kudos to Narendra for
organizing the event. I'm including some feedback from Narendra in this
recap.
HIGHLIGHTS
=
On Mon, 2011-02-07 at 06:
Greetings,
In case you were planning on attending tomorrow's Test Day, the FreeIPA
v2 [1] previously scheduled for Thursday, February 10 (tomorrow) has
been rescheduled. Several issues and bugs have slowed the preparation.
Those issues should be resolved shortly.
The FreeIPA v2 Test Day will now
# F15-Alpha Blocker Review meeting
# Date: 2011-02-11
# Time: 17:00 UTC (12:00 EDT, 09:00 PDT) [1]
# Location: #fedora-bugzappers on irc.freenode.net
Here are the current bugs listed as blocking the Alpha release of Fedora
15. We'll be discussing all of these to determine if they meet the
Alpha r
=
#fedora-bugzappers: F-15-Alpha Blocker Bug Review
=
Meeting started by jlaska at 17:00:20 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-02-11/f15alpha-bu
Greetings folks,
I'm passing along an announcement from the freeipa-users mailing list
[1] regarding the first of two Test Days next week. On Tuesday, we'll
be hosting a test day focused on FreeIPA v2.
The FreeIPA project implements an identity server. IPA stands for
Identity, Policy and Audit (
Just a reminder ... the FreeIPA v2 test day is going on right now. Come
join the fun in #fedora-test-day.
https://fedoraproject.org/wiki/Test_Day:2011-02-15_FreeIPAv2
Thanks,
James
On Sat, 2011-02-12 at 10:31 -0500, James Laska wrote:
> Greetings folks,
>
> I'm passing along a
On Tue, 2011-02-15 at 11:28 -0700, Orion Poplawski wrote:
> On 02/15/2011 10:40 AM, Felix Miata wrote:
> > On 2011/02/15 08:36 (GMT-0500) James Laska composed:
> >
> >> Good-bye install.img, hello initrd.img!
> >
> >> https://fedoraproject.org/wiki/Anaco
1 - 100 of 133 matches
Mail list logo
