X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B3C6.517A063A@onstor-exch02.onstor.net>; Wed, 20 Jun 2007 21:37:55 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B3C6.517A063A"
Content-class: urn:content-classes:message
Subject: Zonda branch open for business - Was: RE: Perforce
Date: Wed, 20 Jun 2007 21:34:09 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D312@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Zonda branch open for business - Was: RE: Perforce
Thread-Index: Acezk0GK5WcyWRgMQXmzNsgonrbVQQABMZx6AACjg7AACs1Aeg==
References: <BB375AF679D4A34E9CA8DFA650E2B04E0436142D@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Jay Michlin" <jay.michlin@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B3C6.517A063A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Good evening. The Zonda project branch has been unlocked and is ready to =
go. Tomorrow I will release seed builds from the branch as requested, =
start the Coverity project runs for the new project, and merge the final =
few bits in from the DeLorean RTM.

If there are any problems please let me know ASAP, thanks.

-Ken


-----Original Message-----
From: Jay Michlin
Sent: Wed 6/20/2007 5:25 PM
To: Ken Renshaw; Paul Hammer
Subject: RE: Perforce
=20
Thanks Ken and Paul. I forwarded your message to dl-software, and they =
will appreciate it.

jay=20

-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, June 20, 2007 5:14 PM
To: Paul Hammer
Cc: Jay Michlin
Subject: RE: Perforce

Every branch except for zonda is available and there have been numerous =
checkins from developers to them. The zonda branch will be unlocked this =
evening after I finish importing Jobi's latest changes. No checkins have =
been lost to my knowledge, I've released builds for 2.2.2.x, 2.2.3, =
3.0.0, and FB-NOSAMBA so far.=20

The only trouble I've seen is some confusion about the state of the =
files in people's workspaces, i.e. work in progress at the time of the =
crash. Since we rolled back to the previous night's backups as a =
baseline Perforce has no way of knowing about files people have edited =
during that time, so all they need do is what I've been telling people =
since the start: keep a copy of your tree before doing anything and =
simply reopen the files for edit. Larry sent out basically this same =
thing to the cougar crowd yesterday, and I worked with Ron and others to =
make sure they understood.=20

It's never fun when your SCM system goes belly-up, and losing some of =
the current state and having to recreate changelists is unfortunately =
unavoidable.

Once the last branch zonda is up I'll send out a note to the group and =
asking them to let me know if they're having issues. If i dont' know I =
can't help them :)

Thanks,

-Ken


-----Original Message-----
From: Paul Hammer
Sent: Wed 6/20/2007 4:32 PM
To: Ken Renshaw
Cc: Jay Michlin
Subject: Perforce
=20
Hey Ken,
=20
Are all of the branches back up, unlocked and available for checkins in =
perforce, specifically Zonda, the FB-Samba (calsoft branch) and 223 =
branches?=20
=20
Did we loose any data/checkins in the outage last week on these =
branches. I thought as of Thursday that everything was checked out and =
back up and running without issue.
=20
Several members of Dev have not been able to complete their checkins =
since Perforce went down last week. Some have noted that it looks like =
the work they were doing and it may be lost. Can we please get to the =
bottom of this one ASAP and make sure everything is operational.=20
=20
Ken please send an update to the team once you think every thing is =
copasetic and lets make sure that everyone is able to access perforce =
and checkin their work.
=20
Thanks,
=20
-Paul



------_=_NextPart_001_01C7B3C6.517A063A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Zonda branch open for business - Was: RE: Perforce</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Good evening. The Zonda project branch has been =
unlocked and is ready to go. Tomorrow I will release seed builds from =
the branch as requested, start the Coverity project runs for the new =
project, and merge the final few bits in from the DeLorean RTM.<BR>
<BR>
If there are any problems please let me know ASAP, thanks.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jay Michlin<BR>
Sent: Wed 6/20/2007 5:25 PM<BR>
To: Ken Renshaw; Paul Hammer<BR>
Subject: RE: Perforce<BR>
<BR>
Thanks Ken and Paul. I forwarded your message to dl-software, and they =
will appreciate it.<BR>
<BR>
jay<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Wednesday, June 20, 2007 5:14 PM<BR>
To: Paul Hammer<BR>
Cc: Jay Michlin<BR>
Subject: RE: Perforce<BR>
<BR>
Every branch except for zonda is available and there have been numerous =
checkins from developers to them. The zonda branch will be unlocked this =
evening after I finish importing Jobi's latest changes. No checkins have =
been lost to my knowledge, I've released builds for 2.2.2.x, 2.2.3, =
3.0.0, and FB-NOSAMBA so far.<BR>
<BR>
The only trouble I've seen is some confusion about the state of the =
files in people's workspaces, i.e. work in progress at the time of the =
crash. Since we rolled back to the previous night's backups as a =
baseline Perforce has no way of knowing about files people have edited =
during that time, so all they need do is what I've been telling people =
since the start: keep a copy of your tree before doing anything and =
simply reopen the files for edit. Larry sent out basically this same =
thing to the cougar crowd yesterday, and I worked with Ron and others to =
make sure they understood.<BR>
<BR>
It's never fun when your SCM system goes belly-up, and losing some of =
the current state and having to recreate changelists is unfortunately =
unavoidable.<BR>
<BR>
Once the last branch zonda is up I'll send out a note to the group and =
asking them to let me know if they're having issues. If i dont' know I =
can't help them :)<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Paul Hammer<BR>
Sent: Wed 6/20/2007 4:32 PM<BR>
To: Ken Renshaw<BR>
Cc: Jay Michlin<BR>
Subject: Perforce<BR>
<BR>
Hey Ken,<BR>
<BR>
Are all of the branches back up, unlocked and available for checkins in =
perforce, specifically Zonda, the FB-Samba (calsoft branch) and 223 =
branches?<BR>
<BR>
Did we loose any data/checkins in the outage last week on these =
branches. I thought as of Thursday that everything was checked out and =
back up and running without issue.<BR>
<BR>
Several members of Dev have not been able to complete their checkins =
since Perforce went down last week. Some have noted that it looks like =
the work they were doing and it may be lost. Can we please get to the =
bottom of this one ASAP and make sure everything is operational.<BR>
<BR>
Ken please send an update to the team once you think every thing is =
copasetic and lets make sure that everyone is able to access perforce =
and checkin their work.<BR>
<BR>
Thanks,<BR>
<BR>
-Paul<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B3C6.517A063A--
