AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070711160319.2262a293@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jobi.ariyamannil@onstor.com>,<ken.renshaw@onstor.com>,<dl-engineering@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	BB375AF679D4A34E9CA8DFA650E2B04E047C35DE@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 11 Jul 2007 16:03:34 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
Cc: "Ken Renshaw" <ken.renshaw@onstor.com>, "dl-Engineering"
 <dl-engineering@onstor.com>
Subject: Re: Zonda branch going away tomorrow at 9 AM
Message-ID: <20070711160334.2afd5a97@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E047C35DE@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D436@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E047C35DE@onstor-exch02.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

There should be no additional requirements.  If any requirements turn
up that are "out of the ordinary" please let someone on the cougar team
know about it.  We've been very persistent about making sure that
everything that used to work still works the same way as expected.

Thanks,

a


On Wed, 11 Jul 2007 15:59:46 -0700 "Jobi Ariyamannil"
<jobi.ariyamannil@onstor.com> wrote:

> Hi,
> 
> When the cougar branch is ready for business, could you make a build
> out of it so that we can move all our filers cleanly to the new
> build ?  Are there any additional requirements while upgrading filers
> from zonda to cougar?
> 
> Regards,
> Jobi
> 
> -----Original Message-----
> From: Ken Renshaw 
> Sent: Wednesday, July 11, 2007 2:56 PM
> To: dl-Engineering
> Subject: Zonda branch going away tomorrow at 9 AM
> Importance: High
> 
> Did that get your attention? :)
> 
> As most already know, we are going to be merging the project branches
> for Zonda and cougar and going forward using a single branch for
> EverON development. Tomorrow morning at 9 AM I will be locking the
> Zonda branch for good and pushing the code through main and into the
> cougar branch. This means that whatever opened work you have against
> the Zonda branch must be checked in tonight or you will have to
> migrate the changes manually into a new workspace.
> 
> The plan going forward is this, worked out with Larry and the cougar
> team:
> 
> # Get developers to submit any outstanding Zonda change lists
> # Lock the ZONDA branch (it is now dead)
> # Integrate latest in ZONDA to main
> # Integrate cougar with latest in main
> # Developers submit all outstanding work/changes for the cougar branch
> # Fix any last minute build issues, etc.
> # Zonda submittal three comes from the cougar branch
> # The cougar branch is locked and at end of life (avoid the problem of
> check-ins after submittal)
> # The cougar branch is pushed to main
> # The dev branch is created from main
> # All future Zonda submittals come from the dev branch until the Zonda
> release branch is created.
> 
> I'm not sure at this time when the third submittal for Zonda will be
> requested, but as noted above it will come out of the cougar branch.
> After a successful Zonda submittal the rest of the plan will be
> carried out, effectively closing all open project branches and
> creating a single branch called 'dev' for all ongoing EverON
> development.
> 
> I will check the nightly buildlogs in the morning to make sure the
> Zonda code builds cleanly and if so I'll lock the branch and that
> will be that. I will send out an email in the morning once the
> process has begun, and another once the cougar branch is ready for
> Zonda developers.
> 
> If there are any questions please let me know.
> 
> Thanks also to Larry for all his work and brainstorming with me on
> this.
> 
> -Ken
> 
> 
> 
> 
