This section defines the lifecycle of Verne Releases and Verne Product Features.
- A Release is a new instance of the Verne Product Suite that typically contains Product Defect fixes, Product Enhancements, and when applicable, new Product Features. A Release is categorised as a major upgrade, and can be supported by numerous builds associated with the Release.
- A Product Feature is a new area of functionality within the Product Suite, which is made available for use by Clients, (subject to any applicable restrictions or considerations) for the term of its life.
Included in these sections are the classifications of the States that define the lifecycle.
Release Lifecycle Policy
Release Issue/Availability
A Release will be made available to Clients once it has passed Foster Moore testing and acceptance. It is strongly recommended that Clients keep up to date with the latest Release wherever practical, as this ensures that the latest features and functions are available, and mitigate risk around a ‘big bang’ upgrade. A number of subsequent builds will be provided for each Release as the product functionality is enhanced and any quality issues are addressed.
Release Naming/Numbering Convention
The combination of a Release name and associated build will adhere to the following convention:
aaa (Build b.c.d) where:
- aaaa represents the Release name. Such upgrades usually contain major new Product Features;
- b represents the major build number associated with the Release;
- c represents a minor build number associated with the Release. Such builds usually contain minor new Product Enhancements as well as reported Product Defect fixes and improvements to security, performance and stability;
- d represents a patch build number associated with the Release.
Release Documentation
Product Release documentation will be generated and made available to Clients as complementary documentation to associated Project Release Notes. Included in the Product Release documentation will be details of:
- New Product Features;
- Improvements and Enhancements;
- Product Defects raised as a result of, and explicitly associated to Project Issues.
The Lifecycle States
A major Release proceeds through a lifecycle of States. These States are, in reverse chronological order as follows:
Support for Lifecycle States
Minor builds to support the availability of new Product Enhancements as well as reported Product Defect fixes and improvements to security, performance and stability will be issued against major Releases that fall into the Current and Supported States. Unless there are exceptional circumstances such as a critical security fix, such fixes will be provided as the latest build.
Minor and patch builds will be issued against major Releases that fall into the Notice State at Foster Moore’s discretion.
Foster Moore are under no obligation to provide support for major Releases that fall into the Retired State unless a Client’s contract expressly states otherwise.
Timeline Guides to States
Major Releases that fall into the Supported State will remain in that State for a minimum of 2 years before a Notice of Intention to Retire is issued.
Major Releases that fall into the Notice State will remain in that State for a minimum of twelve months following the issue of the Notice of Intention to Retire.
Product Feature Lifecycle Policy
A Verne Product Feature is a component within the Verne Product Suite that offers specific, autonomous features and functionality. It may be necessary to discontinue a Feature for a variety of reasons, including lack of demand, technology obsolescence or the availability of successor Features. Once a Feature moves toward its end of life, important milestones regarding the Feature will be communicated to Clients through this phase.
Feature Issue/Availability
A new Product Feature will be made available to Clients once it has passed Foster Moore testing and acceptance. It will be introduced into the latest Release, but may also be included in supporting build for a previous Release at Foster Moore’s discretion.
It is strongly recommended that Clients keep up to date with the latest Release wherever practical, as this ensures that any Features introduced become available for consideration.
The Feature Lifecycle States
A Feature will be subject to a lifecycle of States. Feature States are, in reverse chronological order as follows:
Feature Support for Lifecycle States
The support for a Feature is dependent on the Feature State and the Release State that the Feature is present in. The support matrix can be summarised in the table below, and the subsequent explanations:
Feature Support
(1) Minor builds to support the availability of the Feature will be issued against major Releases that fall under the Current and Supported Release States.
(2) Minor builds to support the availability of the Feature will be issued against major Releases that fall under the Notice Release State at Foster Moore’s discretion.
(3) Foster Moore are under no obligation to provide support for the Feature for Releases that fall into the Retired State unless a Client’s contract expressly states otherwise.
End Of Life
(1) Minor builds to support the availability of the Feature will be issued for major Releases that fall under the Current and Supported Release States.
(2) Minor builds to support the availability of the Feature will be issued against major Releases that fall under the Notice Release State at Foster Moore’s discretion.
(3) Foster Moore are under no obligation to provide support for the Feature for Releases that fall into the Retired State unless a Client’s contract expressly states otherwise.
Feature Retired
(3) Foster Moore are under no obligation to provide support for the Feature that falls into the Component Retired State unless a Client’s contract expressly states otherwise.
Timeline Guides to States
Features that fall into the End of Life State will remain in that State for a minimum of 1 year before the Feature becomes Retired.
