AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090420173532.6a3d2b57@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>,<andy.pinkard@onstor.com>,<dl-Leopard@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31284FEF89B@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 20 Apr 2009 17:35:44 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sandrine Boulanger <sandrine.boulanger@onstor.com>
Cc: Andy Pinkard <andy.pinkard@onstor.com>, dl-Leopard
 <dl-Leopard@onstor.com>
Subject: Re: Update of Beta Site prior to GA?
Message-ID: <20090420173544.32c8f85e@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB31284FEF89B@exch1.onstor.net>
References: <20090420172658.7c2d33b4@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB31284FEF89B@exch1.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

On Mon, 20 Apr 2009 17:30:17 -0700 Sandrine Boulanger
<sandrine.boulanger@onstor.com> wrote:

> The bigger problem is that we have not demonstrated so far that 1.1.7 fixed the cifs share access with AD only, so far it's still failing.

Ah, OK, I didn't know that.  Nevermind then ~:^)

> -----Original Message-----
> From: Andy Sharp 
> Sent: Monday, April 20, 2009 5:27 PM
> To: Andy Pinkard
> Cc: dl-Leopard
> Subject: Re: Update of Beta Site prior to GA?
> 
> On Mon, 20 Apr 2009 10:36:01 -0700 Andy Pinkard
> <andy.pinkard@onstor.com> wrote:
> 
> > I really would like to get the UK site (at least) to 1.1.7 via the approved upgrade process and demonstrate that the CIFS share issues in their envirnment have been fixed (following the QS guide workflow)
> > 
> > I can get access to that system on probably a 1/2 day notice to schedule the upgrade time.
> 
> 
> Hopefully I'm not speaking out of school by saying that you should be
> able schedule that for tomorrow.  I won't know how to update the CS
> repository until tomorrow, but you should be able to perform the upgrade
> after I do that.  I'm just a touch concerned about the bogus lines
> added to the sources.list file, but that's not show-stopper for this
> case.
