Skip to content

Latest commit

 

History

History
69 lines (47 loc) · 3.23 KB

RELEASE_HISTORY.md

File metadata and controls

69 lines (47 loc) · 3.23 KB
Raw

Zowe CLI Releases

Zowe follows a regular release schedule with major versions released every two years and minor versions approximately every six weeks. Full details regarding the Zowe release schedule are available on zowe.org and the Zowe Community Github.

Zowe Release Schedule

Zowe v3.x LTS Releases

Version Release Date Status Release Notes
v3.0.0-prerelease 2024-08 Under Development

Major Release Timeline

Zowe Major Releases

Version Timeframes

  • Active: Each major version remains in this phase for 2 years, receiving regular updates and new features.
  • Maintenance: Following the Active phase, each major version remains in this phase for an additional 2.5 years, receiving only critical fixes and security patches.
  • Under Development: The pre-Active phase where the next major version is prepared. This phase varies in length and is not available for general consumption.

Guarantees

  • Critical Defects Fixes: The community will fix critical defects. The criteria for what constitutes a critical defect can be found here.
  • Extender Conformance: Extenders achieving Zowe conformance for the long-term support version will not need to modify their product to remain functional when Zowe updates are provided within the same major version.

Recommendations

  • Production: Use Active or Maintenance releases for production due to the guaranteed stability and the community’s commitment to fixing critical defects.
  • Nightly Builds: Available for integration testing. Use at your own risk.

Zowe Release Process

Short Summary

  1. Code Freeze date is hit.
  2. Each squad provides a version of the code to integrate into the Release Candidate (RC).
  3. RC is built and tested with an automatic test suite.
  4. RC is deployed and tested by squads.
  5. RC is approved by the TSC vote.
  6. Release is published.
  7. Documentation is published.
  8. Release retrospective is held.

Release Numbering

Releases follow semantic versioning guidelines (MAJOR.MINOR.PATCH).

  • MAJOR: Incompatible API changes.
  • MINOR: Backwards-compatible functionality additions.
  • PATCH: Backwards-compatible bug fixes.

Release Content

The following components of the release are managed by the CLI squad:

  • CLI Component
    • CLI Core
    • CLI Plugins
  • Client SDKs
    • Node.js Client SDK
    • Python Client SDK

Zowe CLI Squad