End of Support for Zowe Version 1: Transitioning to Future Versions

Jakub Balhar
Zowe
Published in
4 min readFeb 9, 2024

{Core} The Open Mainframe Project’s Zowe version 3 is coming and as a result, version 2 is transitioning to the maintenance release while version 1 support is ending. To better understand what that means for you, continue reading!

Here comes the sunset for version 1

Since April 2020, Zowe version 1 has been in the Long Term Support (LTS) phase, marking a period of stability and maintenance for users. In April 2022, the “active” release of Zowe transitioned to version 2, initiating a new phase of continuous feature & capability delivery and stabilizing version 1 as the maintenance-only version. As we approach September 2024, we announce the End of maintenance support for version 1.

Understanding Support Phases:

  • Active Release: This phase is characterized by the active development and release of new features. With the anticipated release of version 3, it will become the primary focus of our development efforts. Consequently, version 2 will no longer receive new features.
  • Maintenance Release: In this phase, a version receives only security updates and critical bug fixes. Version 2 is transitioning to this phase, ensuring stability and security for users not ready to move to version 3. However, to access new features, upgrading to version 3 will be necessary.

Critical Dates and Actions:

Where are we?
  • The last update for version 1 is scheduled for the latter half of September 2024. Beyond this point, no further releases, including security updates, will be provided for version 1.

What Should You Do?

  • As Version 1 Consumers: It’s essential to upgrade to at least version 2 before the end of support date on September 30, 2024, to ensure continued support and security.
  • As Version 2 Consumers: Provided there is no immediate need for new capabilities, remaining on version 2 is a viable option.

Where do I get help?

Security considerations for migration off V1

On Sept 30, 2024, the end of support date, the following Zowe Community processes terminate:

  • Dependency scans that identify vulnerabilities — vulnerabilities will remain in the code regardless of whether they reside in dependencies or directly in Zowe code
  • Static analysis code reviews that uncover potential issues
  • Pipeline builds & code tests

If you want to read more about our security policy, it’s available here: https://www.zowe.org/security

Steps for Transition:

  1. For users of Zowe version 1: Plan your upgrade to version 2 as soon as possible. To assist in this transition, we’re updating the migration guide, available at Zowe Documentation.
  2. Looking Ahead: Users on version 2 should start preparing for the eventual transition to version 3 to take advantage of new functionalities and improvements.

Best practices for upgrading from V1 to V2:

If you want to learn more about what changed on the V2 boundary, please consult:

For the client-side you probably want to follow the installation guides unless the software was updated automatically:

For the server-side the recommendation is to create a clear installation of V2 and migrate to it. The guide for Zowe V2 installation is here

Conclusion:

The planned end of support for Zowe version 1 signifies a significant milestone in the project’s evolution. By staying informed of these changes and preparing for upgrades, users can ensure they benefit from the latest features, security, and support offered by Zowe. To stay informed join our mailing list (https://lists.openmainframeproject.org/g/zowe-user)

If you enjoyed this blog checkout more Zowe blogs here. Or, ask a question and join the conversation on the Open Mainframe Project Slack Channel #Zowe-help, #Zowe-announcements or #Zowe-onboarding. If this is your first time using the Open Mainfrane slack channel register here.

--

--

Jakub Balhar
Zowe
Writer for

I always try to find answers to the complex questions. Now exploring the world of Mainframes in the Broadcom inc.