Axiad Product Lifecycle Policy
- 19 Dec 2023
- 4 Minutes to read
- Print
- DarkLight
- PDF
Axiad Product Lifecycle Policy
- Updated on 19 Dec 2023
- 4 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Important Information
The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing. Axiad shall have no liability for any error or damages of any kind resulting from the use of this document.
The Axiad Software referenced in this document is licensed to you under the terms and conditions accompanying the software or as otherwise agreed between you or the company that you are representing.
Axiad is committed to assisting customers with their products throughout the product lifecycle, and as products are updated and enhanced. This Lifecycle Policy provides consistent and predictable guidelines for the availability of support throughout the life of a product and is intended exclusively for the benefit of Axiad customers with respect to the product(s) they purchased.
Versioning
All Axiad products are released with a version of the format <MAJOR>.<MINOR>.<PATCH>. All updates to a product will always be released under a new version.
Major Releases (x.0)
Major releases may:
introduce non-backwards compatible API changes.
retire older APIs where appropriate.
require major migration processes (database and otherwise).
Typically, these versions introduce significant feature additions and product structure.
Minor Releases (x.x)
Minor releases may:
introduce new functionality
introduce new APIs
update or modify user interface and user experience changes where appropriate
introduce database changes via a product-rchestrated upgrade.
All APIs are committed to be backward-compatible with the behavior set in the prior minor release(s) of the same major release.
Patch Releases (x.x.x)
Patch releases will include:
bug fixes
security updates
Patch releases may:
update or modify user interface and user experiences based on critical or high-priority bug fixes.
UI flow and concept changes are avoided wherever possible.
Where appropriate for the product, DB changes will also be avoided unless unavoidable due to a bug fix. P
Patch releases enforce all guarantees of backward-compatibility described as commitments of minor release changes.
Lifecycle Phases and Milestones
The lifecycle phases and milestones described below only apply to major and minor releases. Patch releases do not extend the shelf life of a product version.
Overview
When a new version of the product is released, the previous GA version immediately moves to End of Sales (product and security patching only).
Six months after the End of Sales date, it is moved to End of Maintenance (security patching only).
Six months from the End of Maintenance date, it is moved to End of Life, where it stays until the product is announced as legacy, or a new major version is released.
General Availability (GA) | End of Sales (EOS) | End of Maintenance (EOM) | End of Life (EOL) | |
|---|---|---|---|---|
Product Availability | √ | X | X | X |
Maintenance |
|
Limited to defect fixes, and critical security issues |
Limited to defect fixes, and critical security issues | X |
Support | √ | √ |
|
Assistance based on quote |
General Availability (GA)
The GA date indicates when a new product release is available for sale (it can be ordered, fulfilled, and supported).
During this period, the software release will be:
maintained with upgrades, updates, Service Packs, and Hot Fixes created for new functionality and/or defect fixes; and
supported under active Maintenance & Support agreements.
If minor releases or patch releases are made available, customers may be required to transition to the most recent release for bug fixes and maintenance as it represents the superset of functionality for the product release.
GA Summary
Product available for sale.
Fully-sustained engineering with new functionality and/or bug fixes.
Full technical support.
End of Sales (EOS)
The EOS date indicates when a specific software release will no longer be available for purchase. A release automatically transitions from GA to EOS when a new major or minor release of the product is made available by Axiad. During this period, the software release will be:
maintained with patch releases created to address defects; and
supported under active maintenance & support agreements.
Customers may be required to transition to the most recent patch release for bug fixes and maintenance as it represents the superset of functionality for the product release.
EOS Summary
Product no longer available for sale.
Limited sustained engineering with minor enhancements and defect fixes only.
Full Technical Support.
End of Maintenance (EOM)
The EOM date indicates when a specific product release will have no further code-level maintenance other than security-related updates deemed critical by Axiad. Security issues could be related to publicly-identified (or other) security vulnerabilities.
A release transitions to EOM 6 months after its EOS date.
When the software release reaches EOM, Axiad no longer maintains the release (major or minor) and patch releases are longer be created. Code fixes other than those required to address critical security issues are no longer provided.
On the EOM date, support will transition from full support to limited technical assistance via telephone, email, and web. Axiad Technical Support will direct customers with issues to existing fixes, patches, and workarounds applicable to the reported case, and may direct customers to upgrade to a more current version or release of the software.
EOM Summary
Product is no longer available for sale.
Minimal sustained engineering with critical security issues only.
Limited technical support.
End of Life (EOL)
The EOL date indicates when security related maintenance builds, technical support through phone, e-mail or e-service, and product downloads will no longer be available.
A release transitions to EOL 6 months after its EOM date.
IMPORTANT INFORMATION
Axiad reserves the right to change the timeframe at its sole discretion based on business needs or technical risk for customers.
Once the EOL date has been reached, Axiad no longer provides standard technical support for the software release. Technical assistance may be available on a commercially reasonable basis only and will require a specific quote.
Software images may be removed from the download site. Product information will be limited to whatever material may be available online and is subject to removal at a future date.
Axiad will notify customers with a valid maintenance agreement of End-of-Life dates.
EOL Summary
Product is no longer available for sale.
No sustained engineering.
No standard technical support, but technical assistance may be available based on quote.
Was this article helpful?
