Choosing a Version Number for Application Code?
One of the common rules-of-thumb used for choosing a displayed version number string for a new version of a layered product or an application, its implications, and its expected effects on client applications and users, follows: o No functional and no application-visible changes, bugfixes only-the edit number is incremented. These tend to be very small, very isolated, or ECO- level changes. These can also be distributions for specific hardware configurations or platforms, as is the case with an OpenVMS Limited Hardware Release (LHR). Application rebuilds are not expected, and there is an assumption that general user-provided application-related regression testing will not be required. o Minimal functional and very few user-visible changes-the maintenance number is incremented. These tend to be very small or even ECO-level changes, though somewhat larger than an edit-level change. Application rebuilds are not expected, and there is an assumption that user-provided application-related re
Related Questions
- Describe the advantages of writing a managed code application instead of unmanaged one. What’s involved in certain piece of code being managed?
- Can international users download the application? Is it possible for international users to download the beta version?
- Choosing a Version Number for Application Code?
