FUSE Product Lifecycle and Support Policy
The following product information is designed to communicate the FUSE product lifecycle plans, product development, and technical support resources that will be available during a FUSE product’s life span. This document outlines the different product stages from first customer shipment (FCS) through the eventual retirement of the product.
Lifecycle Phases and Definitions for FUSE Products
The table below describes the product development efforts, technical support services, and software availability policies during the five phases of a FUSE product’s life cycle. A complete description of each phase is given below.
| Phase | New Features | Maintenance releases/patches | Available on fusesource.com | Supported |
| Incubating | yes | yes | yes | limited |
| Active | yes | yes | yes | yes |
| Functionally stable | no | yes | yes | yes |
| Mature | no | no | yes | yes |
| Retired | no | no | no | 18 months |
Current Phase of FUSE Releases
The table below lists the phase for each release of the FUSE products. A complete description of each phase is given below.
| Product | Incubating | Active | Stable | Mature | Retired |
| FUSE ESB | 4.2 | 3.4 | 3.3.1 | 3.3.0 and below | |
| FUSE Message Broker | . | 5.2, 5.3 | 5.0, 5.1 | . | 4.x and below |
| FUSE Services Framework | . | 2.2 | 2.0, 2.1 | . | . |
| FUSE Mediation Router | . | 2.2, 2.3 | 1.4, 1.5, 1.6 | 1.3 | 1.2 and below |
| FUSE JBI Eclipse Tools | . | . | . | . | 1.1 and below |
| FUSE HQ | 4.2 | 3.2 | 3.1 | . | . |
Phase Descriptions
Incubating Stage
FUSE products in the Incubating Phase will receive new features and enhancements to current features. Maintenance releases will be created against products in the Incubating Phase to address known issues. Incubating products are specifically not recommended for production usage. Limited technical support services are available for Incubating products. No guarantee of compatibility is provided for products that are evolving in incubation. Documentation and code samples are made available in draft mode and are actively evolving in this stage. Support issues will be handled in a best effort manner with a reduced SLA. The current Incubating products will be available on fusesource.com.
Active Phase
FUSE products in the Active Phase will receive new features and enhancements to current features. Maintenance releases will be created against products in the Active Phase to address known issues. There will be an ongoing patch process that will make sure that critical or customer-impacting bugs are addressed. Full technical support services are available for Active products. The current Active products will be the primary releases available on fusesource.com.
Functionally Stable Phase
No new features or significant enhancements will be made to products in the Functionally Stable Phase. Critical bugs that significantly impact continued customer deployment would be considered for patching during this phase. Full technical support is available for Functionally Stable products. The current Functionally Stable products will be available on fusesource.com.
Mature Phase
During the Mature Phase there will be no new features or enhancements added to FUSE products. Mature products will not be patched. Although Technical Support will continue to provide a minimal level of support for Mature products for a minimum of 18 months, they will encourage customers to upgrade to the current Active release. Mature products will be available on fusesource.com.
Retired Phase
Once a FUSE product enters the Retired Phase it will not be enhanced or available on fusesource.com. It will be supported for a period of 18 months under a Retired Product Support offering. After this period, the product will no longer be supported.
Versioning Scheme for FUSE Products
The FUSE products follow the version numbers of the Apache project, which are determined by the projects Project Management Committee (PMC).
Lifecycle Phase Policy for FUSE Products
The current lifecycle phase of FUSE products may change whenever a Major or Minor version is released. When any version is released it is initially an Active release. When a Minor version is release the previous version becomes Mature, and when a Major version is released the previous version may or may not become Mature. Multiple Major releases may be considered Active at a given time, but only one Minor release per version is considered Active at a given time. Mature releases become Retired at the discretion of Product Management.