X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C70EAA.80865A18@onstor-exch02.onstor.net>; Wed, 22 Nov 2006 18:53:06 -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 18:53:06 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0138C33D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E01335F70@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: product version numbering
thread-index: AccOnRIbXiOsgJiNT8mVBTz7VdW8vAAAEa7wAAJ9rH0AAIXNDwAAICQg
From: "Chris Vandever" <chris.vandever@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Angela Elliott" <angela.elliott@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"dl-Clio" <dl-Clio@onstor.com>,
	"dl-lambo" <dl-lambo@onstor.com>
Cc: "Caeli Collins" <caeli.collins@onstor.com>

My understanding is that we expect most customers will bypass clio and
upgrade directly to lambo.  In that case it would make sense to focus
our doc efforts there for the complete doc set, and try to get a waiver
for clio as Ken suggested.

Just my $.02.

ChrisV

-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, November 22, 2006 6:45 PM
To: Angela Elliott; Paul Hammer; Tim Gardner; dl-Clio; dl-lambo
Cc: Caeli Collins
Subject: RE: product version numbering

Maybe not change, but an exception made this time. If we truly expect
lambo to follow clio so closely, then we can maybe skip one of the two
first release doc-wise and only do full sets for either clio or lambo
and delorean, which would space the doc releases further out.

Just a comment, I'm not sure of the total impact of all of this to you
Angie, nor the marketing requirements.

Thanks, this is indeed an important question to bring up now.

-Ken


-----Original Message-----
From: Angela Elliott
Sent: Wed 11/22/2006 6:40 PM
To: Paul Hammer; Tim Gardner; dl-Clio; dl-lambo
Cc: Caeli Collins
Subject: RE: product version numbering
=20
For tech pubs it is important to know the version number of a release as
soon as possible because:

- If the first and/or second digit of the version change, acc. to the
current directives set up for tech pubs, I am required to do a full set
of books (6 at present) + online help (2 at present) + release notes.=20

- If only the third and/or fourth digit in the version number changes, I
am required to do release notes only.

- If only the fourth digit in the version number changes, no
documentation requirements exist, except the readme files done by
engineering.=20

So if the version numbers outlined by Tim are the correct ones, I would
be required to do a full set of books + online help + release notes by
Jan. 8, only a couple of weeks after the release of the Clio books,
online help, and release notes . I think most of you have a good enough
understanding of the amount of tech pubs work required to do a full
documentation release to understand that a turn around of a couple of
weeks from one full release with 6 books, 2 online help files, and 1
release note to the next is humanly impossible.

So perhaps the requirements for tech pubs need to change?

-angie=20


-----Original Message-----
From: Paul Hammer
Sent: Wed 11/22/2006 5:29 PM
To: Tim Gardner; dl-Clio; dl-lambo
Subject: RE: product version numbering
=20
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




