On Tue, 26 Feb 2013 08:37:01 -0700
Tim Flink wrote:
> There has already been a thread here on this topic [1] but after it
> came up in the Fedora QA meeting yesterday, we decided to make an
> actual proposal.
>
> [1]http://lists.fedoraproject.org/pipermail/test/2013-February/113898.html
As agre
On 01/03/13 12:19 AM, Kamil Paral wrote:
By the way, I see this topic relevant just for developers of one of Fedora QA
apps, it doesn't really influence the testers community in any way - the email
notifications influence them (and the solution is clear there), not the trac
location. So I wou
On Fri, 2013-03-01 at 09:20 +, "Jóhann B. Guðmundsson" wrote:
> On 03/01/2013 08:19 AM, Kamil Paral wrote:
> > By the way, I see this topic relevant just for developers of one of Fedora
> > QA apps, it doesn't really influence the testers community in any way - the
> > email notifications inf
On Thu, 2013-02-28 at 16:51 -0700, Tim Flink wrote:
> > To solve this, we have a couple of options:
> >
> > 1. Start using the defaultcc plugin for trac such that emails for the
> > blocker tracking app are directed to a new qa-devel@ list
> >
> > 2. Move all development related tickets out of t
On 03/01/2013 03:18 PM, Tim Flink wrote:
On Fri, 01 Mar 2013 09:20:05 +
"Jóhann B. Guðmundsson" wrote:
On 03/01/2013 08:19 AM, Kamil Paral wrote:
By the way, I see this topic relevant just for developers of one of
Fedora QA apps, it doesn't really influence the testers community
in any wa
On Fri, 01 Mar 2013 09:20:05 +
"Jóhann B. Guðmundsson" wrote:
> On 03/01/2013 08:19 AM, Kamil Paral wrote:
> > By the way, I see this topic relevant just for developers of one of
> > Fedora QA apps, it doesn't really influence the testers community
> > in any way - the email notifications inf
On Fri, 01 Mar 2013 07:51:00 +
"Jóhann B. Guðmundsson" wrote:
> On 02/28/2013 11:51 PM, Tim Flink wrote:
> > On Tue, 26 Feb 2013 08:37:01 -0700
> > Tim Flink wrote:
> >
> >> There has already been a thread here on this topic [1] but after it
> >> came up in the Fedora QA meeting yesterday, w
On 03/01/2013 08:19 AM, Kamil Paral wrote:
By the way, I see this topic relevant just for developers of one of Fedora QA
apps, it doesn't really influence the testers community in any way - the email
notifications influence them (and the solution is clear there), not the trac
location. So I wo
> > There hasn't been much of a response to this yet, so I'm assuming
> > that
> > everyone is OK with the idea of (1) and keeping the blocker
> > tracking
> > app bugs on the fedora-qa trac. If we're going to migrate to a new
> > trac instance, I'd rather do it soon (in the next week) since we're
On 02/28/2013 11:51 PM, Tim Flink wrote:
On Tue, 26 Feb 2013 08:37:01 -0700
Tim Flink wrote:
There has already been a thread here on this topic [1] but after it
came up in the Fedora QA meeting yesterday, we decided to make an
actual proposal.
[1]http://lists.fedoraproject.org/pipermail/test/
On Tue, 26 Feb 2013 08:37:01 -0700
Tim Flink wrote:
> There has already been a thread here on this topic [1] but after it
> came up in the Fedora QA meeting yesterday, we decided to make an
> actual proposal.
>
> [1]http://lists.fedoraproject.org/pipermail/test/2013-February/113898.html
>
> The
On Tue, 26 Feb 2013 11:58:46 -0500 (EST)
Kamil Paral wrote:
> > To solve this, we have a couple of options:
> >
> > 1. Start using the defaultcc plugin for trac such that emails for
> > the blocker tracking app are directed to a new qa-devel@ list
>
> I don't expect blocker bugs app to grow int
> To solve this, we have a couple of options:
>
> 1. Start using the defaultcc plugin for trac such that emails for the
> blocker tracking app are directed to a new qa-devel@ list
I don't expect blocker bugs app to grow into monstrous dimensions (should I?),
so I don't see a problem keeping it i
There has already been a thread here on this topic [1] but after it came
up in the Fedora QA meeting yesterday, we decided to make an actual
proposal.
[1]http://lists.fedoraproject.org/pipermail/test/2013-February/113898.html
The concern raised is that notifications for development related ticket
14 matches
Mail list logo
