X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C70EA2.59658064@onstor-exch02.onstor.net>; Wed, 22 Nov 2006 17:54:45 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: product version numbering
Date: Wed, 22 Nov 2006 17:54:44 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E017B36DB@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EC2DDBF@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: product version numbering
thread-index: AccOnRIbXiOsgJiNT8mVBTz7VdW8vAAAEa7wAAEfQmUAABBrwA==
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"dl-Clio" <dl-Clio@onstor.com>,
	"dl-lambo" <dl-lambo@onstor.com>


Well, it turns out that QA was confused about it - you just didn't know=20
of your confusion until I pointed it out to you :)


-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, November 22, 2006 5:51 PM
To: Paul Hammer; Tim Gardner; dl-Clio; dl-lambo
Subject: Re: product version numbering

I agree with Paul's recollection  as to the original versioning scheme
Jerry wanted. If it's to be changed that's fine, but some of us weren't
confused about it ;)

-Ken

=20

-----Original Message-----
From: Paul Hammer
To: Tim Gardner; dl-Clio; dl-lambo
Sent: Wed Nov 22 17:29:22 2006
Subject: RE: product version numbering

Pretty sure this is incorrect,  Lambo is a 2.1.1 (as per Jerry's
request) and Delorean may be 2.2 or something else, yet to be
determined. Would not use these external versioning in the code to block
things like upgrades, the versions numbers may very well change, that is
why we are using the project names so that the shipping version numbers
can change right up to the end as our business decisions change. =20
=20
Lets decouple the versions completely from the project names. If we need
an internal version number that should be designed into the product and
not be forced to depend on the version string that is created during the
packaging step (consistent with the approach you suggested for mirroring
support during the Clio time frame). We know that the versioning issue
has already bitten us several times due to changes in the business.
=20
-Paul

________________________________

From: Tim Gardner
Sent: Wed 11/22/2006 5:16 PM
To: dl-Clio; dl-lambo
Subject: product version numbering



There was some confusion in the dev meeting today with regard to product
version numbering.

I confirmed the following numbering scheme with Jay:

Clio            2.1.0.0

Lambo           2.2.0.0

DeLorean        2.3.0.0

This was discussed and agreed to in the first lambo project planning
meeting.

This is the numbering scheme that development is coding to.

Tim


