I would like to request a review of two new packages that are a result
of pytest splitting off from libpy so that they can be included in F16.
pycmd - https://bugzilla.redhat.com/show_bug.cgi?id=675588
pytest - https://bugzilla.redhat.com/show_bug.cgi?id=675587
I am not the maintainer for these p
# F16 Alpha Blocker Review meeting #3
# Date: 2011-07-29
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
It's once again time for everyone's favorite activity - blocker bug
review meeting time !!
Fedora 16 has branched and the first Alpha
This is a little later than originally planned, but the Fedora 15
(yes, Fedora 15 - not a typo) EC2 test day will be on this Thursday
2011-08-04 [1].
Fedora 15 AMIs are available for testing and are listed on the test
day wiki page [1]. The tests are designed to ensure basic functionality
for the
# F16 Alpha Blocker Review meeting #3
# Date: 2011-08-12
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
The Fedora 16 alpha release has been pushed back a week, so we get
another blocker bug review meeting for alpha!
The next Fedora 16 A
===
#fedora-bugzappers: F16 Alpha Blocker Bug Review Meeting #5
===
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-08-12/fedora-bugzappers.2011-08-12-17.02.html
Minute
# F16 Beta Blocker Review meeting #2
# Date: 2011-09-02
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
The second action packed beta blocker review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through
# F16 Beta Blocker Review meeting #3
# Date: 2011-09-09
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
The third installment of the irresistible beta blocker bug review
meeting series will be this Friday at 17:00 UTC in #fedora-bugzappers
# F16 Beta Blocker Review meeting #4
# Date: 2011-09-15
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
"Another blocker bug review meeting?! I can't wait!"
- Anonymous source
The next blocker bug revie
# F16 Beta Blocker Review meeting #5
# Date: 2011-09-23
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The fifth (and hopefully final) Fedora 16 beta blocker bug review
meeting will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll
be running
On Fri, 23 Sep 2011 16:20:43 -0700
Adam Williamson wrote:
> If you want to help test 16.19, tflink is working on a boot.iso and
> I'm uploading a live image, both of which include the newer anaconda.
> We'll mail when those are available. Please don't bother with any
> more testing of the updates
# F16 Final Blocker Review meeting #1
# Date: 2011-09-30
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
I apologize for the late notice on this - we usually don't start on the
blocker review meetings until the week after beta. However, we already
ha
At the Fedora 16 Beta Go/No-Go Meeting yesterday, the Fedora 16 Beta
release was declared GOLD! Fedora 16 beta will be released on Tuesday,
October 4, 2011.
Major thanks to everyone who made this happen. There is no way that we
could have gotten all this done without everyone's hard work and
assis
# F16 Final Blocker Review meeting #2
# Date: 2011-10-07
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The second Fedora 16 final blocker bug review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the
final
On Sun, 9 Oct 2011 11:05:28 +0200
Till Maas wrote:
> On Sat, Oct 08, 2011 at 11:43:58PM +0200, Christoph Wickert wrote:
>
> > 3. Can someone (I'm looking at you, QA) make sure all
> > extensions are still compatible?
>
> The problem is that testers seem to ignore test cases provided for
>
On Sat, 08 Oct 2011 23:43:58 +0200
Christoph Wickert wrote:
> 3. Can someone (I'm looking at you, QA) make sure all extensions
> are still compatible?
Anyone with a FAS account can pull updates from updates-testing and
provide karma to those updates. Karma giving isn't limited to th
On Sun, 9 Oct 2011 13:16:52 +0200
Thomas Spura wrote:
> It would be great, when bodhi would allow me to add an updated
> mozilla-noscript to the firefox update, when I notice, that the new
> firefox upadate in testing breaks it.
> Otherwise, firefox is pushed to stable more faster, than
> mozilla
Since the beta criterion for running Fedora as a Xen guest (DomU) was
removed for Fedora 16, there has been some discussion [1] [2] on test@
about whether or not we should add it back for Fedora 16 final. The old
criterion read:
The release must boot successfully as a virtual guest in a situatio
# F16 Final Blocker Review meeting #3
# Date: 2011-10-14
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The third Fedora 16 final blocker bug review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the
final b
On Mon, 10 Oct 2011 12:09:51 -0600
Tim Flink wrote:
> Are there any objections to moving forward with this? There seems to
> be no objections from the kernel maintainers who have been
> participating in the discussion on test@ but we wanted a bit more
> devel input before moving for
The Fedora 16 cloud test day is going on today in #fedora-test-day.
The main test day page [1] lists the details on all of the projects
that are taking part in the test day. If you're interested, stop by and
help test any or all of:
- Aeolus [2]
* Aeolus is software for running virtual mac
# F16 Final Blocker Review meeting #4
# Date: 2011-10-21
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The fourth Fedora 16 final blocker bug review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the
final
# F16 Final Blocker Review meeting #5
# Date: 2011-10-28
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The fifth Fedora 16 final blocker bug review meeting will be this
Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the
final b
Bodhi comments were enabled earlier today in AutoQA and as some have
noticed, old updates are being tagged as failed even though they have
already been pushed to stable updates.
We are aware of the issue and are working on it. We will send out
another email once the issue has been resolved.
Tim
On 03/23/2011 11:19 AM, Tim Flink wrote:
> Bodhi comments were enabled earlier today in AutoQA and as some have
> noticed, old updates are being tagged as failed even though they have
> already been pushed to stable updates.
>
> We are aware of the issue and are working on it. W
Rolling on with the Fedora 15 Test Days, we have the Printing test day
this week:
https://fedoraproject.org/wiki/Test_Day:2011-03-29_Printing
This event will focus on all aspects of printing; including printer
setup, printer sharing and printing jobs.
In previous Fedora releases the application
On 03/31/2011 01:17 PM, Orion Poplawski wrote:
> This doesn't seem right. Can't compare across releases?
At the moment, this is expected behavior. Rpmguard only compares builds
within a release or, more specifically, within a koji tag (dist-f16 in
this particular case).
If you would like to see
On 04/10/2011 07:39 PM, Bruno Wolff III wrote:
> On Sun, Apr 10, 2011 at 18:19:26 -0700,
> Christopher Aillon wrote:
>>
>> I just realized today for the first time that our nightlies are based on
>> stable, not testing. I think that's something we need to address. It's
>> probably still usef
On 04/09/2011 05:31 AM, drago01 wrote:
> On Sat, Apr 9, 2011 at 12:57 PM, Tomasz Torcz wrote:
>> On Sat, Apr 09, 2011 at 05:32:04AM +0200, Kevin Kofler wrote:
>>> Will Woods wrote:
In fact, there's plenty of approvers available, but you're not engaging
with them. They might not know how
On 04/11/2011 01:21 AM, Christopher Aillon wrote:
> On 04/11/2011 12:13 AM, Tim Flink wrote:
>> On 04/10/2011 07:39 PM, Bruno Wolff III wrote:
>>> On Sun, Apr 10, 2011 at 18:19:26 -0700,
>>>Christopher Aillon wrote:
>>>>
>>>> I just reali
On 04/16/2011 01:52 PM, Axel Thimm wrote:
> Hi,
>
> I built two sets of security updates for f13/f14/f15 and autoqa rejected
> the f13/f14 packages. It looks like autoqa is waiting for the packages
> to be properly pushed to f stable before green-lighting the
> matching package for f. Do I have to
The Cloud SIG test day for Fedora 15 is will be this Thursday [1]. The
focus will be on using BoxGrinder [2] and Amazon Elastic Compute Cloud
(EC2) [3] with Fedora 15.
BoxGrinder is "a set of projects that help you grind out appliances for
multiple virtualization and Cloud providers." Another way
On 04/27/2011 03:00 PM, James Laska wrote:
> 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.
On 04/28/2011 02:00 AM, Kamil Paral wrote:
>> Keeping the current way will just make me (and possibly others)
>> add filters to throw away messages from AutoQA. Please be aware of
>> how much contributor time you waste by making them hope through
>> useless (because the tests have passed and no inf
I've been a Fedora user since FC5 but hadn't contributed until I started
working for Red Hat earlier this year as part of Fedora QA, spending
most of my time on AutoQA. Prior to starting at Red Hat, I was working
on an internal test automation framework for storage device firmware.
I was planning
AutoQA will be affected by the infrastructure changes announced last
week [1]. During the outage, AutoQA tests will not be run and feedback
will not be posted to Bodhi.
At this point, we are expecting the outage to last at least a day while
the systems are re-racked and we reconfigure AutoQA for t
As a heads up, we're updating AutoQA to 0.7 today. I'm not expecting
any issues during the update process but no new jobs will be run while
we're updating the production systems. The update process shouldn't
take much more than an hour, maybe two if we hit problems.
If all goes well, you might not
This will make for two weeks in a row, but I don't think that we have
any agenda items for Monday and obviously, there isn't anything to
follow up with from last week.
If you know of any topics that should be discussed, please add them to
the wiki page (https://fedoraproject.org/wiki/QA/Meetings/2
# F17 Alpha Blocker Review meeting #1
# Date: 2012-01-27
# Time: 17:00 UTC [1] (13:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
We're approaching the F17 alpha release and it's time for the first F17
blocker review meeting! I'm sure everyone's excited to get these
meetings
On Thu, 26 Jan 2012 12:22:58 -0700
Tim Flink wrote:
> # F17 Alpha Blocker Review meeting #1
> # Date: 2012-01-27
> # Time: 17:00 UTC [1] (13:00 EDT, 09:00 PDT)
> # Location: #fedora-bugzappers on irc.freenode.net
Correction on the time:
17:00 UTC, 12:00 EST, 09:00 PST
Sorry for th
# F17 Alpha Blocker Review meeting #2
# Date: 2012-02-03
# Time: 17:00 UTC [1] (12:00 EST, 09:00 PST)
# Location: #fedora-bugzappers on irc.freenode.net
The second F17 alpha blocker bug review meeting will be this Friday at
17:00 UTC in #fedora-bugzappers. We'll be running through the final
blocke
# F17 Alpha Blocker Review meeting #3
# Date: 2012-02-10
# Time: 17:00 UTC [1] (12:00 EST, 09:00 PST)
# Location: #fedora-bugzappers on irc.freenode.net
The third F17 alpha blocker bug review meeting will be this Friday at
17:00 UTC in #fedora-bugzappers. We'll be running through the final
blocker
On Tue, 21 Feb 2012 14:54:13 +
Nelson Marques wrote:
> Hi,
>
> Please forgive my lack of knowledge, but could you please provide a
> link to a .iso ? :)
You can find the images at:
- http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.RC3/
Tim
signature.asc
Description: PGP signature
--
# F17 Beta Blocker Review meeting #1
# Date: 2012-03-02
# Time: 17:00 UTC [1] (12:00 EST, 09:00 PST)
# Location: #fedora-bugzappers on irc.freenode.net
It's that time again! The first F17 beta blocker bug review meeting
will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll be
running throu
# F17 Beta Blocker Review meeting #3
# Date: 2012-03-16
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT - note the DST change)
# Location: #fedora-bugzappers on irc.freenode.net
I'm sure that everyone is struggling to hold back their excitement but
worry not - the next blocker bug review meeting is al
With the upgrade to bodhi2, the method we were using to notify
packagers of check failures (bodhi comments) is not working at the
moment due to some of the api changes which came with the upgrade.
We're working to restore the comments and eventually transition over to
fedmsg emission but in the me
On Wed, 26 Aug 2015 14:34:14 -0600
Orion Poplawski wrote:
> https://bodhi.fedoraproject.org/updates/libwps-0.4.1-1.fc21
>
> depchecklibwps-0.4.1-1.fc21(x86_64) a
> day ago
>
> shows passed:
>
> TAP version 13
> 1..1
> ok - depcheck for Koji build libwps-0.4.1-1.fc21
>
On Wed, 26 Aug 2015 19:05:35 -0600
Orion Poplawski wrote:
> On 08/26/2015 05:04 PM, Tim Flink wrote:
> > On Wed, 26 Aug 2015 14:34:14 -0600
> > Orion Poplawski wrote:
> >
> >> https://bodhi.fedoraproject.org/updates/libwps-0.4.1-1.fc21
> >>
> >>
This has been a long time coming but after running on smaller systems
for the last couple months to make sure that all the parts are running
smoothly, Taskotron is now running in staging:
https://taskotron.stg.fedoraproject.org/
What does this mean? It means that we are almost ready to turn on th
On Mon, 6 Oct 2014 03:49:26 -0400
Rahul Sundaram wrote:
> Hi
>
> I was pushing out updates for deluge for F20 and F19 and when I tried
> to push to stable, AutoQA figured out what this was breaking the
> upgrade path since I had forgotten to do a push for F21. So far so
> good however, the mes
On Mon, 6 Oct 2014 23:17:52 -0400
Rahul Sundaram wrote:
> If there's a sane solution to the problem, it might be possible to
> start
> > doing running upgradepath on updates-testing. However, we don't have
> > any plans to start doing this.
> >
>
> Is it possible to opt-in to get them?
Not re
This has been a long time coming, but AutoQA is no longer scheduling
jobs and Taskotron is now running all of the automated checks on
packages/updates.
The changeover should be transparent to most people - the same checks
are being run in pretty much the same situations. Until Bodhi 2.0 is
deploye
On Tue, 14 Oct 2014 21:10:26 +0200
Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Oct 14, 2014 at 04:28:33AM -0400, Martin Krizek wrote:
> > - Original Message -
> > > From: "Vít Ondruch"
> > > To: devel@lists.fedoraproject.org
> > > Sent: Tuesday, October 14, 2014 8:57:26 AM
> > > Subject
On Wednesday, October 22, 2014 01:43:57 PM you wrote:
> Fedora lacks integration testing (unit testing done during build is
> not enough). Taskotron will be able to fill some gaps in the future,
> so maintainers will be able to set-up various tasks after their
> component is built. But even before
On Fri, 24 Oct 2014 14:10:23 -0600
Tim Flink wrote:
> On Wednesday, October 22, 2014 01:43:57 PM you wrote:
> > Fedora lacks integration testing (unit testing done during build is
> > not enough). Taskotron will be able to fill some gaps in the future,
> > so maintainers w
On Mon, 03 Nov 2014 17:22:27 +0100
Honza Horak wrote:
> On 10/28/2014 08:08 AM, Nick Coghlan wrote:
> > Note that any or all of the above may be appropriate, depending on
> > the exact nature of the specific tests.
> >
> > For example, there are already some public Beaker installer tests at
> > h
On Mon, 03 Nov 2014 17:08:40 +0100
Honza Horak wrote:
> On 10/28/2014 08:08 AM, Nick Coghlan wrote:
> > On 10/22/2014 09:43 PM, Honza Horak wrote:
> >> Fedora lacks integration testing (unit testing done during build
> >> is not enough). Taskotron will be able to fill some gaps in the
> >> future
On Mon, 30 Mar 2015 21:43:56 -0600
Tim Flink wrote:
> On Mon, 30 Mar 2015 16:02:42 -0600
> Tim Flink wrote:
>
> > I'm going to be taking taskotron.stg down for a bit to redeploy it
> > on F21 hosts before beta freeze starts tomorrow.
> >
> > I don'
Planned Outage: Taskotron - 2015-04-23 18:00:00 UTC
There will be an outage starting at 2015-04-23 18:00:00 UTC, which will
last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2015-04-23 18:00:00 UTC
Recently, there have been some invalid failures in depcheck that take
the form of:
package foo-1.2-3.fc21.i686 requires foo-libs(x86-32) = 1.2-3.fc21, but
none of the providers can be installed
foo-libs-1.2-3.fc21.i686 has inferior architecture
This issue has been particularly difficult for us
On Fri, 8 May 2015 16:59:22 +0300
Igor Gnatenko wrote:
> Hi,
>
> I pushed mesa update into F22, but actually testing failed at some
> packages.
>
> I think its not related to my update.
>
> https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/67288/steps/runtask/logs/stdio
>
Planned Outage: Taskotron - 2015-05-11 19:00:00 UTC
There will be an outage starting at 2015-05-11 19:00:00 UTC, which will
last about 15 minutes
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2015-05-11 19:00:00 UTC'
---
Hi everyone,
Roshi and I talked about it today over IRC and neither of us sees
anything that needs to be covered this week - no followup items and
nothing of significant note on test@ over the last week.
The council report will also be on Monday (roshi is covering that) and
that was the only some
Since there is only one currently proposed blocker and F17 beta RC1
should land sometime Friday, there isn't much point in having a blocker
meeting.
Instead, please test beta RC1 once it lands. There are a lot of
accepted blocker bugs - the fixes for them will need testing and
verification.
So, o
# F17 Beta Blocker Review meeting #4
# Date: 2012-03-30
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Since F17 beta has officially slipped a week, we're having another beta
blocker bug review meeting!
The fourth (and hopefully final) F17 beta bl
# F17 Beta Blocker Review meeting #5
# Date: 2012-04-06
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Since F17 beta has officially slipped again, we're having another beta
blocker bug review meeting!
The fifth and final (hopefully for real this
# Fedora Quality Assurance Meeting
# Date: 2012-04-16
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
Apologies for the late notice but we're still planning to hold a QA
meeting in a couple hours. Please
# F17 Final Blocker Review meeting #1
# Date: 2012-04-20
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Now that F17 beta has shipped, it's time to get started on reviewing
the final blockers.
The first F17 final blocker bug review meeting will be
# F17 Final Blocker Review meeting #2
# Date: 2012-04-27
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The second F17 final blocker bug review meeting will be this Friday at
17:00 UTC in #fedora-bugzappers. We'll be running through the beta
blocker
On Wed, 2 May 2012 00:01:23 +0100
Ian Malone wrote:
> On 1 May 2012 19:30, Dennis Gilmore wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi all,
> >
> > the fedora 17 schedule
> > http://fedoraproject.org/wiki/Releases/17/Schedule lists the final
> > change freeze as 2012-0
# F17 Final Blocker Review meeting #3
# Date: 2012-05-03
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Note the non-usual time - Thursday instead of Friday.
We were able to get through some of the blockers at the review meeting
earlier today but t
# F17 Final Blocker Review meeting #4
# Date: 2012-05-04
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Apparently we're trying to set a record for the number of blocker
review meetings in one week. We should get through the rest of them
this time,
# F17 Final Blocker Review meeting #5
# Date: 2012-05-11
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
The next review meeting will be on Friday, 2012-05-11. We'll be running
through the beta blockers and nice-to-haves. An updated list of blocker
On Mon, 14 May 2012 14:56:00 -0700
Luya Tshimbalanga wrote:
> Unfortunately, your suggestion is no use because the screen will stay
> totally black
> after initialization of the installer. =(
If you start the install with sshd as a boot parameter, you'll be
able to ssh in to the installation en
# F17 Final Blocker Review meeting #6
# Date: 2012-05-18
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Apologies about the late notice but the next (and hopefully last)
Fedora 17 final blocker bug review meeting will be today Friday,
2012-05-18.
I don't know if we've talked about it much on list but most of the QA
stuff (autoqa, blockerbugs-dev, taskotron, qadevel) is managed with a
set of ansible playbooks:
https://bitbucket.org/fedoraqa/ansible-playbooks
As we've been adding stuff, these playbooks have been getting more and
more unwiel
On Mon, 10 Mar 2014 08:23:16 -0400 (EDT)
Kamil Paral wrote:
> > Fedora has been accepted as a mentoring org for GSoC 2014 and I'm
> > planning to sign up as a mentor again this year. I'm trying to
> > think of good projects that we could put on the list of suggestions
> > of things that we'd like
On Mon, 10 Mar 2014 13:30:16 -0400 (EDT)
Kamil Paral wrote:
> I've finally had time to watch some DevConf talks I couldn't
> personally attend. This one is very interesting:
>
> http://www.youtube.com/watch?v=rWwugyV9J0Q&index=20&list=PLjT7F8YwQhr928YsRxmOs8hUyX_KG-S0T
>
> I believe we could us
I mentioned this a while ago but just recently figured out the
process details and got the permissions I needed to complete the work.
Our hosts are getting pretty old and most of them haven't seen a
firmware update since they were installed 3-4 years ago. This hasn't
been a problem for most of the
On Fri, 4 Apr 2014 08:50:25 -0600
Tim Flink wrote:
> To be specific, the repos that I'm including in this are:
> - libtaskotron
> - taskotron-trigger
> - resultsdb
> - resultsdb_frontend
> - resultsdb_api
> - pytap13
> - fake_fedorainfra
>
> The settin
On Tue, 08 Apr 2014 13:51:10 +0200
Vitaly Kuznetsov wrote:
> Hi Tim & all,
>
> in Cloud WG we have 'Automatic Smoketests on Image Build' task:
> https://fedorahosted.org/cloud/ticket/38
> AFAIK you have somehting similar among future Taskotron goals. It
> would be nice if we can collaborate here
On Thu, 17 Apr 2014 05:31:30 -0400 (EDT)
Josef Skladanka wrote:
> > https://pythonhosted.org/an_example_pypi_project/sphinx.html#auto-directives
> >
> >
> > I'm not suggesting that we drop everything and fix all the
> > docstrings right now but I am suggesting that we start following
> > the sp
On Thu, 17 Apr 2014 10:03:24 -0400 (EDT)
Kamil Paral wrote:
> > > https://pythonhosted.org/an_example_pypi_project/sphinx.html#auto-directives
> > >
> > >
> > > I'm not suggesting that we drop everything and fix all the
> > > docstrings right now but I am suggesting that we start following
> >
On Fri, 2 May 2014 04:32:52 -0400 (EDT)
Kamil Paral wrote:
> > > > https://phab.qadevel.cloud.fedoraproject.org/w/taskotron-papercuts/
> > >
> > > Thanks, I was thinking about this. It's very unfortunate that
> > > Phabricator doesn't support arbitrary tags/keywords as in
> > > Bugzilla or Trac.
On Tue, 27 May 2014 14:05:41 +0200
Haïkel wrote:
> Awesome !
> My opinion is that QA and WG should cooperate directly: no middle-man.
> We need to have a QA liaison in each WG.
> I didn't see if there's a taskotron hackfest at Flock but I'm looking
> forward having one, be it in the lobby.
There
Planned Outage: taskotron.fedoraproject.org - 2016-01-26 15:00 UTC
There will be an outage starting at 2016-01-26 15:00 UTC, which will
last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2016-01-26
On Thu, 02 Aug 2012 10:23:57 -0700
Adam Williamson wrote:
> We'll be running through the beta blockers and nice-to-haves. An
> updated list of blocker bugs should soon be available: tflink is still
> working on a replacement for the current blocker bugs page, but he
> says he'll have something up
On Tue, 31 Jul 2012 15:35:35 -0500
Michael Cronenworth wrote:
> Adam Williamson wrote:
> [large snip]
> I hate to snip such a large body, but it will save other eyes from
> having to skip past it here.
>
> > Hope that made sense and made things a bit clearer :)
>
> I keep up with the test list
# F18 Alpha Blocker Review meeting #2
# Date: 2012-08-10
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Note: This is the last time that we will be holding the blocker review
meeting on Friday. Future meetings will be on Wednesdays @ 16:00 UTC.
We'
# F18 Alpha Blocker Review meeting #3
# Date: 2012-08-16
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
I'm too used to the meetings being on Fridays. Despite my notice that
future meetings will be on Wednesdays, I forgot to send out an
announcement
# F18 Alpha Blocker Review meeting #4
# Date: 2012-08-22
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Note: This is the new time for regular blocker review meetings
We'll be running through the beta blockers and nice-to-haves. The
current list of
A version of the new blocker tracking app has been up for a little
while but the code is finally public and the app has a new home!
The blocker app now lives at:
http://qa.fedoraproject.org/blockerbugs/
A quick link to the current release blockers is at:
http://qa.fedoraproject.org/blockerbugs/cu
# F18 Alpha Blocker Review meeting #5
# Date: 2012-08-29
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
Note: This is the new time for regular blocker review meetings
We'll be running through the alpha blockers and nice-to-haves. The
current list o
# F18 Alpha Blocker Review meeting #6
# Date: 2012-09-05
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
We'll be running through the alpha blockers and nice-to-haves. The
current list of blocker bugs is available at:
http://qa.fedoraproject.org/bl
# F18 Alpha Blocker Review meeting #7
# Date: 2012-09-12
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
We'll be running through the alpha blockers and nice-to-haves. The
current list of blocker bugs is available at:
http://qa.fedoraproject.org/bl
# F18 Beta Blocker Review meeting #1
# Date: 2012-09-05
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-bugzappers on irc.freenode.net
This is a little earlier than on the schedule, but we already have 30
proposed blockers to run through and waiting longer won't make them go
away.
# F18 Beta Blocker Review meeting #2
# Date: 2012-10-03
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-qa on irc.freenode.net
It's almost time for the next action packed blocker review meeting!
We'll be running through the beta blockers and nice-to-haves. The
current list of blo
# F18 Beta Blocker Review meeting #2.1
# Date: 2012-10-04
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-qa on irc.freenode.net
We were able to get through about half of the proposed blockers in
about 3.5 hours at the review meeting today and decided to continue
tomorrow instead
# F18 Beta Blocker Review meeting #3
# Date: 2012-10-10
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-qa on irc.freenode.net
Given the current count of proposed blockers, I imagine that we will
end up having two meetings again this week. Unless there are objections
or we manage
# F18 Beta Blocker Review meeting #3.1
# Date: 2012-10-11
# Time: 16:00 UTC [1] (12:00 EDT, 09:00 PDT)
# Location: #fedora-qa on irc.freenode.net
Since we didn't get through all of the bugs during the last meeting, we
will have a continuation on 2012-10-11.
We'll be running through the beta block
The next version of QA's blocker tracking app was pushed to production
today. New features include:
- Blocker/NTH Fix Tracking
- Test spin tracking
- Interface re-design
* With help from the design team and Máirín Duffy in particular
- Basic stats on blocker/nth bugs
- Lots of minor fixes
1 - 100 of 282 matches
Mail list logo
