the "wake
people up" category and I definitely don't want people to avoid creating
an incident report because the process implies that all incidents are a
big deal that require disturbing people's sleep.
If we were to have a general incident management policy, I think we
would need to c
Ok, let's try your way and see how it works. Can you please just link
from the IR to your lava bit so there's a two-way link? Thanks...
On Fri, May 11, 2012 at 9:22 AM, Andy Doan wrote:
> On 05/11/2012 08:50 AM, Joey STANFORD wrote:
>>
>> I was hoping we could have one system for this instead of
On 05/11/2012 08:50 AM, Joey STANFORD wrote:
I was hoping we could have one system for this instead of two. Are you
sure that the existing IR process can't be tweaked and used for this
purpose?
My fear is that we'd wind up spamming your list of incidents with stuff
like "panda14's SD card died
I was hoping we could have one system for this instead of two. Are you
sure that the existing IR process can't be tweaked and used for this
purpose?
On Thu, May 10, 2012 at 8:59 PM, Michael Hudson-Doyle
wrote:
> On Fri, 11 May 2012 12:11:36 +1200, Michael Hudson-Doyle
> wrote:
>> On Fri, 11 May
On Fri, 11 May 2012 12:11:36 +1200, Michael Hudson-Doyle
wrote:
> On Fri, 11 May 2012 00:30:26 +0200, Alexander Sack wrote:
> > On Fri, May 11, 2012 at 12:24 AM, Ricardo Salveti
> > > Sure, I just think there are better places for it :-) Based on issues
> > > we had with LAVA and Jenkins at the
On Fri, 11 May 2012 00:30:26 +0200, Alexander Sack wrote:
> On Fri, May 11, 2012 at 12:24 AM, Ricardo Salveti
> > Sure, I just think there are better places for it :-) Based on issues
> > we had with LAVA and Jenkins at the previous cycle, if I had one email
> > for every issue, I'd send at least
