ArubaOS Release Descriptions
The following document describes releases “tags” or descriptions for ArubaOS and InstantOS software releases as used in Aruba WLAN platforms.
Conservative Release (CR)
The Conservative Release tag signifies a release has been deployed in multiple customer production networks. Conservative Releases can be considered as the “gold standard” or “go to” releases within the Aruba WLAN portfolio. Aruba recommends the adoption of Conservative Releases in any customer’s production network.
Conservative Releases may be found on the Aruba Support Site, under the ArubaOS/Conservative Release or Aruba Instant/Conservative Release folders at:
Conservative Releases are typically patched for 18 months following posting of the Conservative Release. Please refer to the Software End-of-Life Policy posted here:
Standard Release (SR)
The Standard Release tag signifies a release introducing significant new software features and/or hardware platforms. Any customer interested in benefiting from new software features or hardware platforms are encouraged to upgrade to a Standard Release. Standard Releases always complete a thorough quality assurance and test cycle before posting and becoming available to all customers. After adoption by multiple customers, Standard Releases may be “promoted” to Conservative Releases.
Standard Releases may be found on the Aruba Support Site, under the ArubaOS/Standard Release or Aruba Instant/Standard Release folders at:
Standard Releases are typically patched for 18 months from initial date of posting of the release. If a Standard Release is promoted to a Conservative Release, the 18-month “patch timer” begins again with the posting of the Conservative Release. Please refer to the Software End-of-Life Policy posted here:
The Technology Release tag signifies the release introduces new software features and/or hardware platforms quickly addressing evolving market requirements. Technology Releases enable Aruba to address unique customer features, product demands or technology enhancements within a short time window. Any customers who desire to adopt these emerging use cases are encouraged to upgrade to Technology Releases. Technology Releases go through an abbreviated quality assurance and test cycle to ensure operation of the new capabilities, but do not go through a complete test cycle to test all known customer use cases as is done with a Standard Release.
The Technology release naming convention adheres to the following pattern [a.b.c.d-featurename] or [a.b.c.d-HWPlatform] where “a.b.c.d” signifies the base Aruba OS version and the featurename/HWPlatform name signifies the new capability being introduced in that particular release.
Technology Releases may be found on the Aruba Support Site, under the ArubaOS/Technology folder at:
The support life cycle for Technology releases tend to be short and typically extends until the features merge into a future Standard Release. There is no defined patch and support cycle for Technology Releases.
In rare instances, a c-build, or customer build, is used to signify a release created to rapidly address a specific customer need, i.e. a unique feature or function, a specific defect fix to address a unique customer environment or adoption of hardware into an “out of cycle” release. A c-build is used as a temporary bridge until the feature, function, fix or hardware can be adopted into a Standard Release. C-builds go through a rapid quality assurance and test cycle for a specific customer use case only. Aruba recommends adoption of c-builds only to address a very specific use case.
C-builds are not supported by the Aruba Technical Assistance Center and are managed directly by the Aruba WLAN Development team. Approval must be given by the WLAN Development team for customers to adopt a c-build. C-builds are not posted to the Aruba Support page. C-builds are “one off” builds and there is no defined patch or support policy.
General Availability (GA)
The General Availability tag was previously used to signify the release has been deployed in multiple customer production networks. The General Availability tag has been replaced by the Conservative Release tag, please see above.
Early Deployment (ED)
The Early Deployment tag was previously used to signify a release recently introducing significant new software features and/or hardware platforms. The Early Deployment tag has been replaced by the Standard Release tag, please see above.