When I was testing the latest F38 nightly yesterday, I hit an issue when trying
to use a kickstart to join an Active Directory domain at install time [1] and
was able to regularly reproduce the issue. If this is reproducible, it's a
pretty clear blocker and I filed it in rhbz:
- https://bugzi
==
#fedora-meeting: Fedora QA Meeting
==
Meeting started by tflink at 16:00:33 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2022-11-14/fedora-qa.2022-11-14-16.00.log.html
.
Meeting summary
+1
I assume that additional meetings would be an option if the need presents
itself, though.
Tim
On 10/31/22 07:38, Luna Jernberg wrote:
+1
On Mon, Oct 31, 2022 at 11:24 AM Geraldo Simião Kutz
wrote:
+1 for te proposal.
geraldosimiao
Em seg, 31 de out de 2022 07:19, Kamil Paral escrev
At some point, we do need to wrap up the TCMS conversation. If not this week
then hopefully next week or the week after.
Tim
On 8/22/22 00:25, Adam Williamson wrote:
Hi folks! I'm proposing we cancel the QA meeting today/tomrrow. I
don't have anything much for the agenda again. There will be a
On 6/22/22 14:13, Adam Williamson wrote:
On Wed, 2022-06-22 at 08:57 -0600, Tim Flink wrote:
3. Continue Using WikiTCMS
On 6/22/22 09:55, Matthew Miller wrote:
On Wed, Jun 22, 2022 at 08:57:04AM -0600, Tim Flink wrote:
3. Continue Using WikiTCMS
This is a follow on from the thread about TCMSs in general. I have a demo of
Kiwi TCMS set up if anyone wants to poke at it:
- https://kiwidemo.fedorainfracloud.org/
Things which aren't available now but would be fixed if we choose to use Kiwi
TCMS going forward:
- anonymous read access is no
This is a conversation which has started a few times but not in anything close
to a formal way. Let's fix that so we at least have an answer of why we're
doing what we're doing :)
A test case management system (TCMS) is pretty much what it sounds like - a
system which manages at least test cas
Taskotron is back up but we're still having some issues with delays to
the incoming jobs.
We're still investigating but data should be flowing again, even if it
is a bit delayed.
Thanks,
Tim
On Thu, 27 Feb 2020 10:09:33 -0700
Tim Flink wrote:
> The subject says it all, really.
&
The subject says it all, really.
Taskotron is having some problems with an internal component, it can't
wait for a better time and we need some downtime to fix it.
If all goes well, it should be back up shortly. I'll send another email
to update once we're done.
Tim
pgpGBXj4uaBN0.pgp
Descripti
On Thu, 28 Nov 2019 08:13:48 -0800
Adam Williamson wrote:
> On Thu, 2019-11-28 at 13:29 +0100, Kamil Paral wrote:
> > What are your thoughts? Does the proposal sound reasonable? Would
> > you change something? Would you use a different backend system?
> > Have I forgotten something important? Fee
On Thu, 05 Sep 2019 11:58:40 -0700
Adam Williamson wrote:
> Hey folks! So, it was suggested at the blocker review meeting on
> Monday that violations of the Basic desktop background criterion:
>
> "The default desktop background must be different from that of the
> last two stable releases."
>
A while back, there was a push to get a beaker [1] instance running in
Fedora. We were able to mostly get it to the point where it was working
but it didn't being used much.
Looking at where we're at today, the time and resources needed to keep
the instance running isn't really worth it and thus,
On Thu, 15 Feb 2018 09:41:02 +0800
Lancelot Mak wrote:
> [lancelot@com kernel-tests]$ ./runtests.sh
> Test suite called with default
> ./default/paxtestSKIP
> ./default/mq-memory-corruption PASS
> ./default/timer-ov
Apologies on not announcing this farther ahead of time.
There will be an outage starting at 2018-01-09 22:00:00 UTC, which will
last 4-6 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2018-01-09 22:00:00 UTC'
Reaso
The outage took a little longer than we planned but everything is back
up and has been running smoothly.
Tim
On Tue, 15 Aug 2017 09:46:47 -0600
Tim Flink wrote:
> Apologies on not announcing this farther ahead of time, the
> announcement slipped through the cracks :(
>
> Ther
Apologies on not announcing this farther ahead of time, the
announcement slipped through the cracks :(
There will be an outage starting at 2017-08-15 16: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
Outage is complete, everything is back up and running.
Please let us know if you see anything not working correctly.
Tim
On Mon, 16 Jan 2017 13:22:20 -0700
Tim Flink wrote:
> There will be an outage starting at 2017-01-17 20:00 UTC, which will
> last approximately 12 hours.
>
>
There will be an outage starting at 2017-01-17 20:00 UTC, which will
last approximately 12 hours.
To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2016-01-17 20:00 UTC'
Reason for outage:
We will be upgrading Taskotron to a new version w
On Thu, 5 Jan 2017 10:42:09 -0700
Tim Flink wrote:
> I realize this is a little last minute but persona has been completely
> shut down now (so auth is no longer possible) and the last issue that
> was preventing migration was taken care of yesterday.
The outage is complete and phabri
I realize this is a little last minute but persona has been completely
shut down now (so auth is no longer possible) and the last issue that
was preventing migration was taken care of yesterday.
I'm planning to take qadevel down (phabricator, some docs etc.)
today so that I can finally replace it
hine ready
for data migration.
Tim
On Thu, 15 Dec 2016 14:34:55 -0700
Tim Flink wrote:
> The outage is taking a bit longer than I had hoped - other production
> systems going down during the outage didn't help :)
>
> I'm still working on this and will send out an email whe
The outage is taking a bit longer than I had hoped - other production
systems going down during the outage didn't help :)
I'm still working on this and will send out an email when it's done.
Tim
On Wed, 14 Dec 2016 10:54:45 -0700
Tim Flink wrote:
> I realize this is a litt
I realize this is a little last minute but there's no telling how much
longer the current auth system will continue to work.
I'm planning to take qadevel down (phabricator, some docs etc.)
tomorrow so that I can finally replace it with an instance that has
working auth among other improvements.
T
On Wed, 7 Dec 2016 08:52:53 -0700
Tim Flink wrote:
> As support for the Persona system has winded down, we finally have a
> new method for logging into our phabricator instance (that should
> also get rid of all those 500s on login).
>
> My goal has been to set up the migration
On Wed, 07 Dec 2016 08:24:46 -0800
Adam Williamson wrote:
> For a start Ipsilon tells me it's some entirely foreign third-party
> domain - 'monikra.me' - that wants access to all my personal
> information, which is a bit unsettling. I went ahead and let it have
> it (For Science!) and got:
FWI
As support for the Persona system has winded down, we finally have a
new method for logging into our phabricator instance (that should
also get rid of all those 500s on login).
My goal has been to set up the migration so that there's no account
fiddling needed to use the new auth system. Things ar
On Mon, 19 Sep 2016 13:49:37 -0700
Adam Williamson wrote:
> On Mon, 2016-09-19 at 12:30 -0600, Tim Flink wrote:
> > This has been announced through other channels but just to make sure
> > folks are aware, there there will be an outage starting at
> > 2016-09-21 21:00
This has been announced through other channels but just to make sure
folks are aware, there there will be an outage starting at 2016-09-21
21:00 UTC, which will last approximately 4 hours.
This will affect all qa systems (amongst others):
- taskotron
- phabricator
- blockerbugs
- openqa
This has been announced through other channels but just to make sure
folks are aware, there will be a planned outage later today for updates
and reboots.
This will affect all qa systems (amongst others):
- taskotron
- phabricator
- blockerbugs
- openqa
There will be an outage starting at
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 Mon, 23 Nov 2015 13:26:54 -0500 (EST)
Kamil Paral wrote:
> > I feel that for something as important as system upgrade, we should
> > provide a better level of quality and assurance for upgrading
> > across 2 releases. Currently we have no criterion and testing it is
> > just an afterthought, n
# Taskotron Outage and Upgrade
# Date: 2015-11-25
# Time: 21:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Length: Approximately 4 hours
There is a larger infra outage scheduled for Wednesday and we're going
to take advantage of that to do an upgrade to production Taskotron. Th
On Wed, 18 Nov 2015 16:36:16 -0800
Adam Williamson wrote:
> #2 MOAR METADATA
>
>
> The alternative is to make the existing Blocker trackers do more work.
> In this model we wouldn't add any new tracker bugs; we'd just add new
> 'magic words' in the Whiteboard field. Right now,
On Sat, 19 Sep 2015 22:36:19 +0800
Ed Greshko wrote:
> With both fedora-easy-karma and fedora-gooey-karma broken what are
> folks using to easily supply feedback on packages in updates-testing?
There is a mostly-working patch attached to the bug about f-e-k:
https://bugzilla.redhat.com/show_bug
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
I don't think that this has gotten much attention yet, so I wanted to
let folks know that Bodhi 2.0 is coming soon - the current working plan
is to upgrade the production bodhi instance next week after folks return
from Flock.
If this plan goes forward, there will be 3-ish weeks (depending on the
===
#fedora-meeting Meeting
===
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-03/fedora-qa.2015-08-03-15.13.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-03/fedora-qa.2015-08-03-15.13.txt
Log:
http://meetb
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
On Tue, 2 Jun 2015 07:02:06 -0400 (EDT)
Kamil Paral wrote:
> Hello,
>
> I have added some notes below.
>
> > The other thing to settle is what we actually want to report. Matt
> > provided the following guidelines:
> >
> > - the current state of the subproject
> > - future plans
> > - th
On Tue, 12 May 2015 15:11:00 -0700
Adam Williamson wrote:
> So, I'd like to get sufficient votes on the proposed blockers and at
> least the significant proposed FEs as soon as possible. Would folks
> prefer voting on-list or in-bug, or having a special meeting, perhaps
> tomorrow (05-13) or Th
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'
---
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
>
On Mon, 04 May 2015 15:43:19 -0700
Adam Williamson wrote:
> so I think it's well enough covered. Would anyone miss the minutes if
> they weren't sent to test@ any more? Thanks!
Wouldn't bother me - I usually look in the meetbot archives first if
I'm looking for something in the minutes anyways
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
On Wed, 8 Apr 2015 12:36:18 -0600
Tim Flink wrote:
> Just wanted to send a heads-up to folks but there was an upgrade to
> RHBZ last night which broke the blockerbugs app's ability to sync with
> bugzilla and the data shown is probably not current.
>
> I'm trying to get
Just wanted to send a heads-up to folks but there was an upgrade to
RHBZ last night which broke the blockerbugs app's ability to sync with
bugzilla and the data shown is probably not current.
I'm trying to get this fixed as quickly as I can but wanted to make
sure folks were aware of the problem s
On Fri, 30 Jan 2015 08:44:03 -0700
Tim Flink wrote:
> I'm not sure what happened but the machine hosting qadevel became
> unresponsive sometime in the last 12 hours and is not recoverable.
>
> I'm going to be rebuilding the host today but until I'm done,
> phabric
On Fri, 30 Jan 2015 14:45:07 -0700
Tim Flink wrote:
> Since qadevel needs to be rebuilt, I'm taking this opportunity to move
> it out of the cloud infrastructure since that's been on my TODO list
> for some time now.
>
> As part of this, the database host for most of t
Since qadevel needs to be rebuilt, I'm taking this opportunity to move
it out of the cloud infrastructure since that's been on my TODO list
for some time now.
As part of this, the database host for most of the QA services needs to
be upgraded.
Taskotron (dev, stg and prod) will be going during th
I'm not sure what happened but the machine hosting qadevel became
unresponsive sometime in the last 12 hours and is not recoverable.
I'm going to be rebuilding the host today but until I'm done,
phabricator and the other services on qadevel will not be available.
I'll update this thread as I make
On Thu, 11 Dec 2014 13:20:40 -0700
Tim Flink wrote:
> I've been putting this off for a while but it's time to actually do
> it.
>
> I'm going to disable username/password logins to phabricator when I
> update it with the newest build next week. The username/passwor
As a heads up, all QA services will be affected by the infra outages
scheduled over the next 3 days: 2014-12-15, 2014-12-16 and 2014-12-17.
Taskotron and Blockerbugs will be affected by all three outages but
Beaker will be less affected due to how it's deployed as a
non-production service.
https:/
# Fedora QA Devel Meeting
# Date: 2014-12-16
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
We had a couple folks who couldn't make the meeting today at the last
minute, so we decided to hold the meeting tomorrow instead
# Fedora QA Devel Meeting
# Date: 2014-12-15
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
Now that F21 is out the door, we can start working a bit more on
tooling. I'd like to spend most of the time discussing the vari
I've been putting this off for a while but it's time to actually do it.
I'm going to disable username/password logins to phabricator when I
update it with the newest build next week. The username/password system
was only meant as a temporary system until we could get FAS auth
working and that's be
The usual suspects for leading the QA meeting are going to be out at
meeting time tomorrow and I'm not up to date enough with the possible
topics to put together a good agenda, so I propose that we cancel the
QA meeting tomorrow.
Of course, if there are topics that need discussion, I'm happy to
fa
On Tue, 14 Oct 2014 19:20:59 -0500
Michael Catanzaro wrote:
> The blocker bugs app [1] seems to have hardcoded links to outdated
> release criteria. Not sure where to file a bug
>
> [1] https://qa.fedoraproject.org/blockerbugs/propose_bug
Wow, that's been around for a while :)
Thanks for l
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, 19 Aug 2014 09:54:01 -0600
Chris Murphy wrote:
>
> On Aug 19, 2014, at 9:22 AM, Tim Flink wrote:
>
> > On Tue, 19 Aug 2014 09:12:24 -0600
> > Chris Murphy wrote:
> >
> >>
> >> On Aug 19, 2014, at 1:18 AM, Christopher Meng
> >&
On Tue, 19 Aug 2014 09:12:24 -0600
Chris Murphy wrote:
>
> On Aug 19, 2014, at 1:18 AM, Christopher Meng
> wrote:
>
> > I don't see the issue here, too.
> >
> > Maybe caused by the special hardware?
>
> Well this is just bizarre. This morning, it's working fine.
> Everything is the same, the
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
The Fedora QA devel team is proud to announce the release of Taskotron
0.3!
This is another incremental improvement and a continuation of our
new-ish timed release process. The new release is running in our
staging instance:
https://taskotron-stg.fedoraproject.org/
The major changes have been:
I just upgraded the version of Phabricator that we have on qadevel [1]
and we now have the ability to do FAS authentication instead of the old
standalone username/password setup.
[1] https://phab.qadevel.cloud.fedoraproject.org/
If you have no idea what I'm talking about, you can probably ignore
===
#fedora-meeting: fedoraqa-devel
===
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-19/fedoraqa-devel.2014-05-19-16.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-19/fedoraqa-devel.2014-
# Fedora QA Devel Meeting
# Date: 2014-05-19
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Now that Taskotron 0.1 has been released, it's time to start planning
for 0.2 so let's do a meeting right after the Fedora QA meet
The Fedora QA devel team is proud to announce the release of Taskotron
0.1!
This is the first of many releases to come. While we are not yet to
the point where AutoQA can be replaced, each new release will bring us
closer to reaching that initial goal. The current plan is to move
towards a time-
==
#fedora-blocker-review: fedoraqa-devel
==
After much fun with finding an open channel for the meeting, we did get
through a bunch of stuff. At the moment, no more meetings are planned
and we will schedule more as needed/app
On Fri, 10 Jan 2014 18:21:28 -0700
Tim Flink wrote:
> # Fedora QA Devel Meeting
> # Date: 2014-01-13
> # Time: 17:00 - 19:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location: #fedora-meeting-1 on irc.freenode.net
There was some miscommunication ab
On Mon, 13 Jan 2014 09:57:05 -0700
Tim Flink wrote:
> On Fri, 10 Jan 2014 18:21:28 -0700
> Tim Flink wrote:
>
> > # Fedora QA Devel Meeting
> > # Date: 2014-01-13
> > # Time: 17:00 - 19:00 UTC
> > (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
>
# Fedora QA Devel Meeting
# Date: 2014-01-13
# Time: 17:00 - 19:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
https://apps.fedoraproject.org/calendar/meeting/271/
Since we didn't quite get through everything on Thursday, we're
co
=
#fedora-meeting-2: fedoraqa-devel
=
We didn't quite get through everything today, so we'll continue after
the QA meeting on Monday.
I'll be sending an announcement for that meeting shortly.
Minutes:
http://meetbot.fedoraproject.
# Fedora QA Devel Meeting
# Date: 2014-01-09
# Time: 16:00 - 18:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-2 on irc.freenode.net
The email feedback I received from folks was from NA and EMEA timezones
and showed a preference for Thursday over Wednes
On Mon, 06 Jan 2014 21:47:33 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 09:39 PM, Adam Williamson wrote:
> > Of course, anything else we can do to free up not just Tim and
> > Kamil, but anyone else with the necessary knowledge and skills, to
> > contribute to tooling work is a good
On Mon, 06 Jan 2014 13:39:35 -0800
Adam Williamson wrote:
> On Mon, 2014-01-06 at 20:20 +, "Jóhann B. Guðmundsson" wrote:
> > On 01/06/2014 05:42 PM, Tim Flink wrote:
> > > I want to focus on getting the base
> > > automation working well so that we can
On Mon, 06 Jan 2014 21:27:44 +
"Jóhann B. Guðmundsson" wrote:
> >> If we want to free time to work on stuff like this Anaconda release
> >> cycle and testing must be finished before alpha or dealt with after
> >> beta.
> > Sure, that could end up being useful but it's but one piece of the
>
On Mon, 06 Jan 2014 20:10:51 +
"Jóhann B. Guðmundsson" wrote:
> Do you think it's wise to be splitting this into seperated meeting
> from the qa meeting?
As much as I'm not really excited about yet another meeting, yes I do
think that it's wise to split this off.
- There is enough to tal
On Mon, 06 Jan 2014 20:20:45 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 05:42 PM, Tim Flink wrote:
> > I want to focus on getting the base
> > automation working well so that we can go to the WGs with "here's
> > our automation system a
I had been thinking about doing this, but John brought it up during the
qa meeting today.
As we're done with both the holidays (read: vacation for many folks)
and F20, it's probably a good time to talk about where we are with the
various qa development projects and what we're going to focus on ove
On Mon, 06 Jan 2014 15:13:48 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 02:52 PM, Matthew Miller wrote:
> > Hi Fedora test and QA folks! I posted a (kind of long) message on
> > Fedora devel with some thoughts about the direction of the project
> > in the next year. A lot of it direc
The AutoQA developers are proud to announce the release of AutoQA 0.8.5
today. This is a maintenance release with the following changes:
- Improved clarity in upgradepath output (#445)
- Updated repository configuration for F20 release
The new version has been deployed to our staging environme
do with packages whose test suite is not suitable to be
> executed during build (e.g. due to requirements or limitations on the
> build servers) ?
>
> What's your take ?
>
> ( Adding Tim Flink to CC to answer from the infrastructure side. )
I'm still unclear on what y
After a bit more of a delay than we were anticipating, blockerbugs
0.4 has been released and deployed to production!
https://qa.fedoraproject.org/blockerbugs/
New features and enhancements:
- Spin requests
* add updates and/or koji builds to the request
- API Support
* get latest blocke
On Tue, 19 Nov 2013 09:25:25 -0700
Tim Flink wrote:
> On Tue, 19 Nov 2013 08:35:07 -0700
> Tim Flink wrote:
>
> > Apologies for the late notice but we are going to be upgrading the
> > blocker tracking app in production today.
> >
> > We're planning to
On Tue, 19 Nov 2013 08:35:07 -0700
Tim Flink wrote:
> Apologies for the late notice but we are going to be upgrading the
> blocker tracking app in production today.
>
> We're planning to start the upgrade at 16:00 UTC and in the worst
> case, will be down for an hour bu
Apologies for the late notice but we are going to be upgrading the
blocker tracking app in production today.
We're planning to start the upgrade at 16:00 UTC and in the worst case,
will be down for an hour but I expect the total downtime to be more
like 15 minutes.
I'll send out another email whe
On Thu, 14 Nov 2013 22:35:02 -0500
Fred Smith wrote:
> Foolish question: What is an "AMI" ??
Amazon Machine Image - images used to boot instances in Amazon's EC2:
http://en.wikipedia.org/wiki/Amazon_Machine_Image
Tim
signature.asc
Description: PGP signature
--
test mailing list
test@lists.
# F20 Beta Blocker Review meeting #6
# Date: 2013-11-06
# Time: 17:00 UTC (12:00 EST, 09:00 PST)
# Location: #fedora-blocker-review on irc.freenode.net
It's time for another round of F20 beta blocker bug review! Please note
the time change to 17:00 UTC due to the recent change in standard time
for
On Fri, 01 Nov 2013 10:12:32 +
"Jóhann B. Guðmundsson" wrote:
>
> On 11/01/2013 10:03 AM, Alexander Todorov wrote:
> > Hi folks,
> > recently OpenSource.com published an article of mine explaining why
> > users should take the extra step to submit a bug:
> > http://opensource.com/business/1
On Fri, 01 Nov 2013 12:03:51 +0200
Alexander Todorov wrote:
> Hi folks,
> recently OpenSource.com published an article of mine explaining why
> users should take the extra step to submit a bug:
> http://opensource.com/business/13/10/user-guide-bugs-open-source-projects
>
>
> It is based on real
On Fri, 01 Nov 2013 12:51:24 +0200
Alexander Todorov wrote:
> На 1.11.2013 12:12, "Jóhann B. Guðmundsson" написа:
>
> > There is nothing in that area that is not already known or trying
> > to be addressed.
> >
>
> I'm not aware of how are we trying to address this, can you point me
> to some
# F20 Beta Blocker Review meeting #6
# Date: 2013-10-30
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
It's time for another round of F20 beta blocker bug review!
We'll be running through the final blockers and freeze exception bugs.
The current li
==
#fedora-blocker-review: f20beta-blocker-review-5.5
==
Minutes:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-28/f20beta-blocker-review-5.5.2013-10-28-16.01.html
Minutes (text):
htt
# F20 Beta Blocker Review meeting #5.5
# Date: 2013-10-28
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
Late notice on monday blocker review meetings seems to be par for
the course as of late - apologies on that. We'll be doing a quick
blocker revi
# Fedora Quality Assurance Meeting
# Date: 2013-10-28
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
Apologies on the late notice, but it's Monday and that means it's time
for the weekly QA meeting. I d
==
#fedora-blocker-review: F20-blocker-review
==
Minutes:
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-23/f20-blocker-review.2013-10-23-16.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fe
On Wed, 16 Oct 2013 02:14:55 + (UTC)
Andre Robatino wrote:
> dlehman proposed https://bugzilla.redhat.com/show_bug.cgi?id=1019500
> as a Beta Blocker, and
> https://bugzilla.redhat.com/show_bug.cgi?id=1019502 as a Final
> Blocker, but both are private, so they need to be fixed before the
> me
On Tue, 15 Oct 2013 15:44:12 -0600
Chris Murphy wrote:
> A bug is set to block final but isn't listed in the tracker. Should I
> file an infrastructure bug, and if so against what component?
>
> Thanks,
>
> Chris Murphy
File it in the qa trac [1] against the blocker bug tracker page, please.
On Fri, 11 Oct 2013 09:24:06 -0600
Tim Flink wrote:
> On Fri, 11 Oct 2013 14:52:28 +
> "Jóhann B. Guðmundsson" wrote:
>
> > On 10/11/2013 02:03 PM, Adam Williamson wrote:
> > > On Fri, 2013-10-11 at 13:42 +, "Jóhann B. Guðmundsson" wrote:
On Fri, 11 Oct 2013 14:52:28 +
"Jóhann B. Guðmundsson" wrote:
> On 10/11/2013 02:03 PM, Adam Williamson wrote:
> > On Fri, 2013-10-11 at 13:42 +, "Jóhann B. Guðmundsson" wrote:
> >
> >> Hmm when was it decided that we should write our own app to
> >> replace the wiki instead of trying to
1 - 100 of 483 matches
Mail list logo
