Build Number Strategy

[Peter Rousseau]

Once upon a time someone had posted an explanation of the components of
a build number, I can't find it.

What should a build number include. Also, do you give build numbers to
individual forms (and reports etc.) or just the 'system'? Thank you.

Peter R

[Ken Loomis]

The best explanation and system I have found is in Software Release
Methodology by Michael Bays in the chapter on Product Release
Classifications and Numbering.

Basically he has 3 numbers separated by periods: 1.2.3
The first number is the version, the second is an update to the
version and the third is a bug fix or correction to the update.

A much more in-depth discussion can be found in the book.

HTH

Ken

[Larry DiGiovanni]

Peter Rousseau wrote:

> Once upon a time someone had posted an explanation of the components of
> a build number, I can't find it.

Are you talking about build numbers or release numbers? Build numbers are
usually just sequential. Version numbers (release numbers) are usually
meaningful.

> What should a build number include. Also, do you give build numbers to
> individual forms (and reports etc.) or just the 'system'? Thank you.

Individual components are typically assigned a simple ascending, integral
version number. System versions are then composed of specific groupings
of component versions.

--
Larry DiGiovanni
Digico, Inc
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources

[Larry DiGiovanni]

Peter Rousseau wrote:

> I guess I'm talking about release numbers, eg, 5.51d.

Corrections, patches, refinement - .. release (e.g, 1.1.1 to 1.1.2)
Minor functional enhancements - . release (e.g., 1.1 to 1.2)
Major functional enhancements - release (e.g., 1.2 to 2.0)

Anything that results in a lack of backward compatibility is a major
release. Same with major changes to the UI.

Most commercial software vendors, particularly in the last 5 years, have
taken to publishing any new version as a new release.