Aspenware Support Policy & Hotfix Process Updates
Aspenware Support Policy & Hotfix Process Updates
At Aspenware, we remain committed to delivering industry-leading tools to support your success. Like any technology company, we have finite resources, so to better focus our efforts on new functionality and platform improvements that drive your business, we will be formally phasing out support for older software versions and legacy features. In the coming months, we will begin deprecating features that are otherwise a drain on our development cycles.
Support Policy Changes
Version Support
To ensure your system stays current and secure:
Aspenware will maintain support for only the two most recent software versions (on a rolling basis). For example, when version 3.7 is generally available for adoption, support for version 3.5 will end.
For unsupported versions, bug fixes will require an upgrade to the latest supported version.
A list of supported versions will be maintained at Aspenware Version Deprecations
While our Customer Success team will continue to provide guidance and answer questions, development work will only be available for supported versions.
Legacy Feature Retirement
Legacy PDPs
Starting with the 3.9 release (Fall 2025), we will phase out support for Legacy PDPs. In practice, we will no longer regression-test or develop fixes for legacy PDP features that are also supported by Cloud PDPs, and we’ll remove the actual code from our solution by version 3.10.
Cloud PDPs have shown a 6% increase in conversion rates through statistically significant A/B testing, provide a more responsive experience for guests, and offer greater feature flexibility for you, our clients.
We strongly recommend enabling Cloud PDPs before setting up your spring, summer, or winter products.
Identity V3 (IDv3)
Our latest identity platform, IDv3, has improved sign-in and sign-up success rates by 23%, while also offering greater security for both guests and resorts. While no formal end-of-support date has been announced for our older identity platform, we strongly recommend migrating to IDv3 before the 2025/26 winter season.
Other Legacy Features
Some legacy features may be retired alongside future Commerce versions. When possible, we will provide alternative product or feature recommendations. However, in certain cases — particularly when a feature is rarely used or no longer aligns with our platform strategy — it may be removed without an alternative.
A schedule to Feature depreciations can be found at Aspenware Feature Deprecations
Hotfix Process Improvements
We’re also working to reduce the overhead associated with hotfixes. As a reminder, hotfixes are isolated, lower-risk fixes used to address urgent or time-sensitive issues that cannot wait for a full release.
Starting with the 3.8 release (estimated June 2025), hotfixes for your current major version will be automatically applied to your UAT environment for testing. This change will simplify validation and reduce manual coordination.
We plan to evaluate this process during the 3.8 release with the goal of introducing automated hotfix deployment with the 3.9 release later in 2025.