AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080909180512.17d85fe3@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ed.kwan@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 9 Sep 2008 18:05:34 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Ed Kwan <ed.kwan@onstor.com>
Subject: the power of escalation
Message-ID: <20080909180534.7063d349@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Ed,

I don't have the power.  To escalate.  I'm not even sure I should
escalate.  But I talked to Rich and he seemed to think that was the
right thing to do.

Bugz

TED00025253 Onstor - 9482 - cluster_lookup_sess: fail to open sess for app clusterrpc

TED00023471 [Cougar] repeating cluster error message on g10r10

The first is dupe'd to the second.  It's a serious bug that needs
attention from Dev ~now~.  The second is P3/Kegg, ie., it's
invisible, as well as being marked MI with no chance of that info ever
being obtained, not from QA and certainly not from Mightydog.

So my question is, what's the procedure to make this go from forgotten
footnote to mega-important-look-at-me-now bug?  Escalation?  Or change
the priority/target for the second bug?  Or?

Cheers,

a

PS Can you think of a good place for me to get some brake pads for the
Schturmvagon?
