Application Lifecycle
As the services offered within TrustX change and evolve the following lifecycle will apply to that we can introduce new functionality as well as remove old / out dated functionality.
Beta: Beta applies to features, API and activities that are still early in its development lifecycle. We may release Beta functionality to production in order to provide customers with access in order to obtain advance feedback. Beta software by its nature will not have full & public documentation sets. Access to Beta is typically on an invite only basis.
Early Access: Early Access applies to features, API and activities that are advanced in its development lifecycle. We may release Early Access functionality to production in order to provide customers with access in order to obtain feedback before moving to Generally Available. Early Access functionality is stable and close to final - it is therefore unlikely that functionality will change, however Daon reserved the right to change functionality , including APIs and activities, if required before functionality is made generally available. For early access documentation will be provided.
Generally Available: Once features, API and activities are full finalized and made public they become Generally Available. At this stage the functionality is fully supported and documented
Deprecated: There a number of reasons that Daon may deprecate functionality - typically this is because the product has evolved and features have been replaced with a superior implementation. Other reasons that software may be deprecated may be due to security concerns, updates of technology (including support of hardware & OS for mobile devices), deprecation of underlying technologies such as OS version etc.
When Daon issues a deprecation notice, customer will be provided with a notice period and provide with an appropriate migration path / strategy. Once the notice period has passed Daon will remove support as outlined in the deprecation notice.
Not all features will go through Beta, EA, GA lifecycle. Some features and functionality may go straight to GA as appropriate. Note for those customer which are part of the ‘preview’ program, they will have access to per-release GA features before they are available in production environments
| Description | Beta | Early Access | Generally Available | Deprecated |
|---|---|---|---|---|
| Contact With Product Team | ✅ | ✅ | ❌ | N/A |
| API Changes | Subject to change | Backwards compatible where possible | Backwards compatible | N/A |
| Daon Support | ❌ | ❌ | ✅ | ✅ |
| Service-Level Agreements | ❌ | ❌ | ✅ | ✅ |
| Announced in Release Notes | ❌ | ❌ | ✅ | ✅ |
| Availability in Preview Environment | By invitation depending on the feature | By request depending on the feature | ✅ | ✅ Deprecated feature will be removed one notice period has passed |
| Availability in Production Environment | By invitation depending on the feature | By request depending on the feature | ✅ | ✅ Deprecated feature will be removed one notice period has passed |
| Documentation | Limited | ✅ Subject to change based on the feedback | ✅ | N/A |
Hotfix Release Process
A hotfix is a swift and specific service update implemented to resolve critical issues significantly affecting the production environment. Usually prompted by a Priority 1 (P1) incident or a security issue, a hotfix is swiftly deployed to address problems that seriously hinder system functionality, which lead to widespread disruptions, or pose a substantial risk to business operations. Additionally, it may occasionally be applied to support urgent customer UI or textual changes.
When a P1 or a major issue arises in the production service and the situation is deemed a very high priority due to the immediate and critical nature of the problem, a hotfix may becomes essential to provide a swift resolution to the problem. The focus of a hot-fix is to deliver a specific and targeted solution to the identified problem without introducing unnecessary changes or updates to the overall system.
Hotfixes are crucial for maintaining the stability and reliability of software systems, especially when unexpected issues threaten to compromise the integrity of the production service. The urgency associated with hot-fix deployment underscores the commitment to ensuring minimal disruption to users and preserving the functionality of essential services. In critical situations where a Priority 1 (P1) or major issue occurs in our production service, the decision to implement a hotfix is paramount.