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
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2018-01-09 22:00:00 UTC'

Reason for outage:

We are upgrading the hosts which run the services required for
Taskotron. This will not affect resultsdb as this will be upgraded at a
later date.

Affected Services:

taskotron.fedoraproject.org

Contact Information:

Please join #fedora-admin or #fedora-noc on irc.freenode.net

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
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2017-08-15 16:00:00 UTC'

Reason for outage:

We are upgrading the hosts which run the services required for
Taskotron.

Affected Services:

taskotron.fedoraproject.org

Contact Information:

Please join #fedora-admin or #fedora-noc on irc.freenode.net

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
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2016-01-17 20:00 UTC'

Reason for outage:

We will be upgrading Taskotron to a new version which requires a
migration that will take 8-12 hours.

One of the features for Taskotron that we've been planning since the
beginning was a way for contributors to maintain their own automated
tasks/tests which would be run during a package's lifecycle.

I'm happy to say that we're almost to this milestone and wanted to get
some feedback from devel@ on the specifics of what we're planning WRT
where these automated tasks will be stored and the execution modes that
we're planning to support.

We have some packages which are in need of review, anyone interested in
a swap?

execdb - Execution status database for Taskotron
* <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1346243" title="https://bugzilla.redhat.com/show_bug.cgi?id=1346243">https://bugzilla.redhat.com/show_bug.cgi?id=1346243</a>

resultsdb_frontend - Frontend for the ResultsDB
* <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1346245" title="https://bugzilla.redhat.com/show_bug.cgi?id=1346245">https://bugzilla.redhat.com/show_bug.cgi?id=1346245</a>

Thanks,

Tim

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
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2016-01-26 15:00 UTC'

Reason for outage:

We will be performing a major upgrade on the production Taskotron
instance which requires downtime while we rebuild and migrate the
backing machines.

Affected Services:

taskotron.fedoraproject.org

Services not listed are not affected by this outage.

Contact Informa

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 mean time, packagers will not receive
notifications if a package they're involved with fails a taskotron
check.

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 somewhat undecided thing from the last QA meeting.

If anyone can think of something worth holding the meeting to discuss,
reply to this mail and we can have a QA meeting at the usual time and
place (15:00 UTC in #fedora-meeting). If there are no replies, consider
the meeting canceled.

Tim

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
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2015-05-11 19:00:00 UTC'

There's a pending security update for the database used by Taskotron
and everything using that database host needs to be stopped while it is
being updated.

The outage will be very short and any jobs which would have been
scheduled during the outage

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 to track down and
while we were finally able to reproduce it on a developer's system, we
don't have a fix for the root cause that we've found.

To keep the issue from affecting any more packagers, we pushed changes
to production Taskotron to mitigate the impact of these invalid
failures.

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
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2015-04-23 18:00:00 UTC'

Taskotron production currently runs on Fedora 20 machines and with that
EOL date coming up, we need to redeploy those machines to a newer
Fedora release.

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
deployed, we're planning to continue providing feedback on updates in
the form of bodhi comments.

While Taskotron is a huge step forwards in terms of having a capable
and maintainable automation system for Fedora, it isn't perfect on the
UX front.

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:

<a href="https://taskotron.stg.fedoraproject.org/" title="https://taskotron.stg.fedoraproject.org/">https://taskotron.stg.fedoraproject.org/</a>

What does this mean? It means that we are almost ready to turn on the
production Taskotron system and turn off AutoQA.

# 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 many countries.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the beta release criteria [1] and should stay on
the list
2.

# 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 list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the beta release criteria [1] and should stay on
the list
2.

# 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 review meeting today in about 20 minutes to go through the new
proposed blockers

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1.

# Fedora Quality Assurance Meeting
# Date: 2013-10-28
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# 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 don't know of many specific topics for
today but figured that we could go over F20 beta status and the
test days for this week and last week. Any other agenda topics welcome!

This is a reminder of the upcoming QA meeting.

# F20 Beta Blocker Review meeting #3
# Date: 2013-10-09
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Everyone's favorite weekly activity is almost upon us once again. We'll
be holding another blocker review meeting tomorrow and while the list
of bugs to review isn't huge, it still promises to be "lots o' fun"!

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1.

# F20 Beta Blocker Review meeting #2
# Date: 2013-10-02
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

It's almost Wednesday and we all know what that means - time to review
some blocker bugs! We've got a decent number of bugs up for review
tomorrow, so join us and help move this process along!

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1.

# F20 Beta Blocker Review meeting #1
# Date: 2013-09-25
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Now that F20 alpha has been released, it's time to start looking at
beta and the already decent sized list of proposed beta blockers and
freeze exceptions.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the beta release criteria [1] and should stay
on the list
2.

# F20 Alpha Blocker Review meeting #6
# Date: 2013-09-18
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Go/No-Go #2 will be on this Thursday, so it's time for what will
hopefully be the last last blocker review meeting for F20 alpha.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.

# Fedora Quality Assurance Meeting
# Date: 2013-09-16
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again on Monday! We did end up slipping release, so
we're still in freeze and have plenty of testing to do.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130916" title="https://fedoraproject.org/wiki/QA/Meetings/20130916">https://fedoraproject.org/wiki/QA/Meetings/20130916</a>

The current proposed agenda is included below.

== Proposed Agenda Topics ==
1. Previous Meeting Followup
2.

We ended up needing a RC2 spin for alpha to fix a bug we thought was
fixed for almost all machines [1] and we're now in the situation where
most of the alpha validation test cases need to be run in less than 12
hours if we don't want F20 alpha to slip.

Fortunately, this is alpha and there aren't nearly so many test cases
to run through but more people to run them would be really appreciated.
If you have some time, grab a Fedora 20 alpha RC2 image [2] and run
through a test case marked "alpha" on either the installation matrix
[3] or the desktop test matrix [4].

If you're more of a cloud pers

# F20 Alpha Blocker Review meeting #5
# Date: 2013-09-11
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Go/No-Go will be on this Thursday, so it's time for what will hopefully
be the last blocker review meeting for F20 alpha.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.

# F20 Alpha Blocker Review meeting #4
# Date: 2013-09-09
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

We're in F20 alpha freeze and you know what that means - monday blocker
review meetings!

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.

# Fedora Quality Assurance Meeting
# Date: 2013-09-09
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again on Monday! We're in the middle of freeze with
go/no-go so the discussion will likely center around F20 alpha testing.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130909" title="https://fedoraproject.org/wiki/QA/Meetings/20130909">https://fedoraproject.org/wiki/QA/Meetings/20130909</a>

The current proposed agenda is included below.

== Proposed Agenda Topics ==
1.

# F20 Alpha Blocker Review meeting #3
# Date: 2013-09-04
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

It's time for the first F20 blocker review meeting post-alpha-freeze!
We've been seeing great participation so far in F20 and would love to
see that continue.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1.

# Fedora Quality Assurance Meeting
# Date: 2013-09-02
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again on Monday! F20 alpha freeze is currently
scheduled for this Tuesday (2013-09-03) so it'll mostly be F20 alpha
status and planning.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130902" title="https://fedoraproject.org/wiki/QA/Meetings/20130902">https://fedoraproject.org/wiki/QA/Meetings/20130902</a>

The current proposed agenda is included below.

== Proposed Agenda Topics ==
1.

# F20 Alpha Blocker Review meeting #2
# Date: 2013-08-28
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Apologies on the late announcement but it's time for the next exciting
installment of "F20 alpha blocker bug review hour(s)"

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.

# F20 Alpha Blocker Review meeting #9
# Date: 2013-08-21
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Well, it's that time again - time to review some blocker and fe bugs
for F20 alpha.

We'll be running through the final blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.