Peer Software Lifecycle Policy

Release Designations

Beta

A Beta release is an early access version of an upcoming release, designed to give customers and partners the ability to try and provide feedback on new functionality.  While Betas typically go through both functional and load testing, Peer Software does not support their use in production environments.

Release Candidate (RC)

A Release Candidate is fully tested and fully supported version that is initially available only to targeted customers and partners.  RC releases are typically made Generally Available after 2 to 4 weeks.

Generally Available (GA)

A Generally Available release is fully tested, fully supported, and available to our entire base of customers with active maintenance or subscription contracts.

Early Access Features

Early Access applies to a specific feature rather than a specific version or release of a product.  Early Access features are made available as part of releases that are in either RC or GA stages.  They are designed to give customers and partners the ability to try and provide feedback on specific new functionality.  While Early Access features typically go through both functional and load testing, Peer Software does not support their use in production environments.

Release Versioning

Peer Software versions software using three digits and a build number, for example v4.5.0.20190801 or v9.4.2.1005.  These digits and build numbers are divided into three identifiers.

Major Releases

The first two digits identify the major version.  A change in either of these digits (for example, v4.5 to v4.6 or v4.5 to v5.0) indicates a major upgrade that requires a new license key.  Major releases introduce significant new features and improvements.  Major releases are typically first available with a Release Candidate designation.

Minor Releases

A change in the third digit (for example, v4.5.0 to v4.5.1) indicates a minor upgrade that does not require a new license key.  Minor releases may include some new functionality but usually focus on performance and other internal improvements.  Minor releases are typically first available with a Release Candidate designation.

Patches

A change in the build number (for example, v4.5.0.20190805 to v4.5.0.20190915 or v9.4.2.1005 to v9.4.2.1006) indicates a patch update.  Patch updates usually include bug fixes and small improvements.  Patches do not typically go through a Release Candidate phase.

Support Lifecycle

Peer Software typically plans for 1 to 2 major releases and 1 to 2 minor releases each year.  Patches are released throughout the year based on customer feedback.  All major releases, minor releases, and patches of a specific product are available to customers with an active maintenance or subscription contract for that product.

As technologies evolve, older releases (and occasionally, even products) become difficult to maintain.  To ensure the best experience, performance, and security for our customers, Peer Software employs two support lifecycle stages for its products.

End of Availability

Releases and products that have reached this stage are no longer under development and are not available for deployment or purchase by new customers.  Support and bug fixes are still available to customers on valid maintenance or subscription contracts, as are renewals of these contracts.  All bug fixes are at Peer Software's discretion.  Customers seeking new functionality will need to upgrade.

Timeframes

• A release reaches End of Availability when a new major release is made Generally Available.  For example, v4.3 reached End of Availability after v4.5 was made Generally Available.
• A product reaches End of Availability at Peer Software's discretion.

End of Support

Releases and products that have reached this stage are no longer supported by Peer Software.  Maintenance and subscription renewals are no longer available for products that have reached this stage.  Customers on subscription contracts will lose access to the software that has reached End of Support once their active subscription expires.  Customers with perpetual licenses that have reached End of Support are welcome to continue using the release or product in their environments.  However, if any support assistance is required, the customer will need to upgrade.

Timeframes

• A release reaches End of Support after three successive major releases are made Generally Available.  For example, v4.1 reached End of Support after v4.2, v4.3 and v4.5 were all made Generally Available.
• A product reaches End of Support once all active maintenance and subscription contracts have expired or have been converted.  This is typically 1 to 2 years after End of Availability but may vary at Peer Software's discretion.

Related articles