AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080627160733.34a51265@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<sandrine.boulanger@onstor.com>,<jobi.ariyamannil@onstor.com>,<jonathan.goldick@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 27 Jun 2008 16:08:46 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>, Sandrine Boulanger
 <sandrine.boulanger@onstor.com>, Jobi Ariyamannil
 <jobi.ariyamannil@onstor.com>, Jonathan Goldick
 <jonathan.goldick@onstor.com>
Subject: sub28beta not ready for prime time (today)?
Message-ID: <20080627160846.7ed3ee70@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 Brian,

Due to the number of bug fixes that are coming in at the last minute,
and some not even in, I don't think we can get away with doing a
two-day smoke test on the submittal and sending it to beta customer
sites.  I'm not comfortable with less than 5 days of non-trivial QA
testing and exercising of the submittal with these changes.  Nor am I
comfortable cutting a submittal without some of these corruption
related fixes included.  The way things are shaping up at this rate,
this submittal has crossed the "it's trivial, just smoke it and ship
it" line.  If I had my way, I would not take the read perf fix at all.

See bug#24469 (and corresponding change 29890 to fix it).  And Max's
read perf fix which Bob wants us to take, and Jobi now says there is
another bug fix that he's working on that will fix a possible data
corruption issue that he thinks might have merit for BMF consideration.

This bug:

Bug#24517 - dcache being copied for writeback can be released too early

Is a perfect example of something that very likely might have been
"uncovered" by Max's previous read perf fix.  If Max found one such bug
this quickly while doing his own testing....
