Categories: RELEASE

Step Platform Release Strategy

Overview

The Step platform follows a structured versioning and release strategy to ensure stability and predictable updates for users. This page describes the versioning scheme, release cadence, and upgrade path for the core Step platform.

Versioning Scheme

Step uses a distinctive versioning format: Major.Minor (e.g., 27.4, 28.3, 29.0)

  • Major version: The first number (e.g., 27, 28, 29) - Incremented for significant releases containing new features and major enhancements
  • Minor version: The second number (e.g., 27.4, 28.3) - Incremented for bug fixes, security patches, and small enhancements

Release Cadence

  • Major releases: Approximately every 3-4 months
  • Minor releases: As needed for bug fixes and security updates

Maintenance Policy

Bug Fixes

Functional bug fixes are included in minor releases and are provided according to the following policy:

  • Each major version receives functional bug fixes for up to one (1) year after its initial release.
  • After this one-year maintenance period, the corresponding major version reaches end of maintenance (EOM) and no longer receives functional updates.
  • Maintenance releases (minor versions) do not introduce new features, ensuring full backward compatibility within the same major line.

Vulnerability Patches

Vulnerability patches are provided for Step Enterprise and SaaS according to the following policy:

  • Vulnerability patches are delivered through minor releases.
  • Vulnerability patches are provided only for the current major version.
  • Older major versions do not receive vulnerability patches as part of the standard license.

Maintenance Principles

Maintenance updates are strictly limited to bug and security fixes, guaranteeing product stability and predictability.

Customers are encouraged to upgrade regularly to the latest major version to benefit from the latest functionality, improvements, and ongoing security maintenance.

Vulnerability Management

The Step platform follows a proactive security vulnerability management process:

Vulnerability Scanning

  • Internal scanning: Performed regularly to identify potential security issues
  • Public documentation: Vulnerability status communicated accordingly

Response Process

When a high or critical vulnerability is discovered:

  1. Assessment: Vulnerability is evaluated and prioritized
  2. Fix delivery: If the vulnerability is fixable, a new release with the fix is delivered within 14 days
  3. Release strategy: Security fixes are delivered through minor releases for the current major version only

This process ensures that security issues are addressed promptly while maintaining platform stability.

Release Information

For detailed information about each release, including new features, enhancements, and bug fixes, please refer to:

Upgrade Path

When upgrading Step, it is recommended to:

  1. Review the Release Notes for breaking changes
  2. Test the upgrade in a non-production environment first
  3. Follow the upgrade procedures detailed in the Installation Guide
  4. Check component compatibility:

Support

For questions about releases or upgrade assistance:

See Also