AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080722112918.40d2bfb2@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sripal.surendiran@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	48860723.4030500@onstor.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 22 Jul 2008 11:29:45 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sripal <sripal.surendiran@onstor.com>
Subject: Re: cougar GA release branch
Message-ID: <20080722112945.64974165@ripper.onstor.net>
In-Reply-To: <48860723.4030500@onstor.com>
References: <20080714142128.5ccd0396@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05B95C8B@onstor-exch02.onstor.net>
	<20080716104500.13531861@ripper.onstor.net>
	<487ED0A8.3070808@onstor.com>
	<48860723.4030500@onstor.com>
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

We'll visit it tomorrow, but I really need some information to make
that call.

What causes this?

What is the end result?  (User has to log in again, filer reboots,
filer explodes, you get the idea)

How hard is it to fix?



On Tue, 22 Jul 2008 21:43:23 +0530 Sripal
<sripal.surendiran@onstor.com> wrote:

> Andy,
> 
> Will this be moved for kegg or we need to fix it Cougar? CQ still
> shows MF for cougar.
> 
> Thanks,
> Sripal.
> 
> Sripal wrote:
> > Update from Triage team regarding moving to Kegg.
> >
> > Andrew Sharp wrote:
> >> What updates are you waiting for?
> >>
> >> On Wed, 16 Jul 2008 00:14:49 -0700 "Sudharsan Srinivasan"
> >> <sudharsan@onstor.com> wrote:
> >>
> >>  
> >>> Hi Andy,
> >>> As of now we have one Cougar MF defect in our list.
> >>>
> >>> Defect  TED00023385 NCM - sscccc:NOTICE: SSL_read() failed,
> >>> errno=11, errmsg (Resource temporarily unavailable) fd(12)
> >>> Owner:Archana.
> >>>
> >>> We have given partial fix. QA said this still occurs. But it is
> >>> very rarely reproducible. We updated the same in CQ and requested
> >>> to move it to Kegg or we need to find a way to reproduce it. We
> >>> are waiting for updates on this defect. Let us know if this can
> >>> be moved to Kegg.
> >>>
> >>> Regards
> >>> Sudharsan
> >>>
> >>>
> >>> ________________________________
> >>>
> >>> From: Andy Sharp
> >>> Sent: Mon 7/14/2008 2:21 PM
> >>> To: dl-software
> >>> Subject: cougar GA release branch
> >>>
> >>>
> >>>
> >>> The cougar GA release branch has been created, it is called
> >>>
> >>> r400rel
> >>>
> >>> The policy, until you hear differently, is for everyone checking
> >>> in P1/P2 fixes to integrate them to the release branch as well,
> >>> no need for extra review from me or anything.  This may change at
> >>> some point in the future.  That means that the dev branch is not
> >>> a dumping ground for untested code -- if it's not tested enough
> >>> to go into the release branch, it's not tested enough to go into
> >>> dev.  You will be notified if/when any of these policies change.
> >>>
> >>> Official "code freeze" is next Thursday.  People who have bugs
> >>> that they don't think they can wrap them up by that time should
> >>> notify the tech lead for that bug.
> >>>
> >>> Cheers,
> >>>
> >>> a
> >>>
> >>>
> >>>     
> >
> 
