On Mon, 23 Mar 2020 10:13:05 -0700
Kevin Fenzi wrote:
> On Mon, Mar 23, 2020 at 03:35:11PM +0100, Dominik 'Rathann'
> Mierzejewski wrote:
> > On Monday, 23 March 2020 at 12:10, Daniel Pocock wrote:
> > [...]
> > > The bottom line is that these tools need to support our
> > > workflows, not try
On 23/03/2020 15:35, Dominik 'Rathann' Mierzejewski wrote:
> On Monday, 23 March 2020 at 12:10, Daniel Pocock wrote:
> [...]
>> The bottom line is that these tools need to support our workflows, not
>> try to shoehorn us into a particular way of working.
>
> Just writing an e-mail about the
On Mon, 23 Mar 2020 10:13:05 -0700
Kevin Fenzi wrote:
> There are a few things that also send emails on their own.
> Sadly, bodhi still does this (even though it should not)
Actually I'm not sad about this; I find the emails from bodhi
considerably more informative than their fedmsg equivalents
On Mon, Mar 23, 2020 at 03:35:11PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Monday, 23 March 2020 at 12:10, Daniel Pocock wrote:
> [...]
> > The bottom line is that these tools need to support our workflows, not
> > try to shoehorn us into a particular way of working.
>
> Just writing an
On Monday, 23 March 2020 at 12:10, Daniel Pocock wrote:
[...]
> The bottom line is that these tools need to support our workflows, not
> try to shoehorn us into a particular way of working.
Just writing an e-mail about the issue to the Fedora devel list will not
change anything, maybe apart from
On 22/03/2020 18:15, Marius Schwarz wrote:
> Hi all,
>
> Am 22.03.20 um 14:19 schrieb Emmanuel Seyman:
>> I feel you've proved the opposite: filing bugs alone isn't sufficient and,
>> apparently, neither is sending out periodic reminders by mail. Perhaps we
>> need to be more agressive in
Hi all,
Am 22.03.20 um 14:19 schrieb Emmanuel Seyman:
> I feel you've proved the opposite: filing bugs alone isn't sufficient and,
> apparently, neither is sending out periodic reminders by mail. Perhaps we
> need to be more agressive in encouraging people to find co-maintainers
> that can help
* Daniel Pocock [20/03/2020 13:22] :
>
> > Over how many bugs and what time period were the requests generated?
>
> More than a year
This is the core of your problem. Not responding to outstanding requests
in a timely manner is a sure way to get more reminders. I suspect
responding to these in a
On Fri, 2020-03-20 at 11:42 -0400, Paul Dufresne via devel wrote:
> > Closing a bug doesn't clear the needinfo. Change the ? to blank under
> > flags (or I'm happy to clear it for you if you'd like).
> Ok, I have done it.
>
> But I believe the outstanding bugs reminder should not include
On Fri, 2020-03-20 at 11:02 -0400, Paul Dufresne via devel wrote:
> About outstanding bugs...
>
> In my opinion, the frequency at which it is sent: every day, is way too often.
> For me, once a month would make more sense.
> Maybe... maybe once a week.
>
> For me, the message contains this is a
On 20/03/2020 13:30, Miro Hrončok wrote:
> On 20. 03. 20 13:22, Daniel Pocock wrote:
>> More than a year
>
> I my humble opinion, if you ignore outstanding Bugzillas for over a
> year, you cannot be surprised you have hundreds of remainders in your
> inbox.
Please remember I've given this
On Fri, Mar 20, 2020 at 3:20 PM Rob Crittenden wrote:
> Closing a bug doesn't clear the needinfo.
I consider that a mis-feature, but I have
learned to live with it.
> As a package owner I like the daily reminder. If it only happened
> monthly then bad timing could make it so I miss a reminder
> Closing a bug doesn't clear the needinfo. Change the ? to blank under
> flags (or I'm happy to clear it for you if you'd like).
Ok, I have done it.
But I believe the outstanding bugs reminder should not include closed bugs!
___
devel mailing list
Paul Dufresne via devel wrote:
> About outstanding bugs...
>
> In my opinion, the frequency at which it is sent: every day, is way too often.
> For me, once a month would make more sense.
> Maybe... maybe once a week.
>
> For me, the message contains this is a one bug:
>
On 20. 03. 20 16:02, Paul Dufresne via devel wrote:
About outstanding bugs...
In my opinion, the frequency at which it is sent: every day, is way too often.
For me, once a month would make more sense.
Maybe... maybe once a week.
Once a day is indeed too much. It used to be once a week.
For
About outstanding bugs...
In my opinion, the frequency at which it is sent: every day, is way too often.
For me, once a month would make more sense.
Maybe... maybe once a week.
For me, the message contains this is a one bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1700171
For most of the
On 20. 03. 20 13:22, Daniel Pocock wrote:
More than a year
I my humble opinion, if you ignore outstanding Bugzillas for over a year, you
cannot be surprised you have hundreds of remainders in your inbox.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
On 20/03/2020 13:19, Emmanuel Seyman wrote:
>
> Hi, Daniel.
>
> * Daniel Pocock [20/03/2020 12:38] :
>>
>> - there were over 100 "outstanding requests" emails in my inbox
>
> Over how many bugs and what time period were the requests generated?
More than a year
>> - there are numerous bugs
Hi, Daniel.
* Daniel Pocock [20/03/2020 12:38] :
>
> - there were over 100 "outstanding requests" emails in my inbox
Over how many bugs and what time period were the requests generated?
> - there are numerous bugs about builds failing, FTBFS
These bugs are signal and not noise.
Not only are
I've been looking at email from Bugzilla to try and find out what I need
to know preparing the upstream release of reSIProcate
I feel the signal/noise ratio is disturbing and it also means I am less
likely to open Bugzilla emails
In particular,
- there were over 100 "outstanding requests"
20 matches
Mail list logo
