Skip to content

Removed EOL information #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Cherabhi wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −240
Open

Removed EOL information #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 2 additions & 12 deletions docs/source/life-cycle.rst
View file
Open in desktop
Copy link
Copy Markdown
Member

@AKippins AKippins May 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: This lifecycle table intentionally retains all releases, including End-of-Life (EOL) versions, to maintain a complete and auditable product history. While EOL releases are no longer supported, their inclusion ensures continuity, supports upgrade planning, and preserves traceability for troubleshooting and compliance purposes.

I'd suggest updating the table so that it's currently accurate rather than deleting the old releases and the links to the the older references. I believe version 1.3 is when the collection became stable so that's the first version listed here.

Original file line number Diff line number Diff line change
Expand Up @@ -20,13 +20,9 @@ Review this matrix for the status of the IBM z/OS core collection version, its c
+------------+----------------+-----------------------+-------------------+-------------------+------------------------+
| Version | Status | Changelogs | GA Date | EOL Date | Life Cycle Phase |
+============+================+=======================+===================+===================+========================+
| 1.6.x | Released | `1.6.x changelogs`_ | x January 2026 | x January 2028 | `Full support`_ |
| 1.6.x | Released | `1.6.x changelogs`_ | January 2026 | January 2028 | `Full support`_ |
+------------+----------------+-----------------------+-------------------+-------------------+------------------------+
| 1.5.x | Released | `1.5.x changelogs`_ | 6 June 2024 | 6 June 2026 | `Maintenance support`_ |
+------------+----------------+-----------------------+-------------------+-------------------+------------------------+
| 1.4.x | Released | `1.4.x changelogs`_ | 17 May 2023 | 9 May 2025 | `End of life`_ |
+------------+----------------+-----------------------+-------------------+-------------------+------------------------+
| 1.3.x | Released | `1.3.x changelogs`_ | 8 February 2023 | 9 February 2025 | `End of life`_ |
| 1.5.x | Released | `1.5.x changelogs`_ | June 2024 | June 2026 | `Maintenance support`_ |
+------------+----------------+-----------------------+-------------------+-------------------+------------------------+

.. .............................................................................
Expand All @@ -36,13 +32,7 @@ Review this matrix for the status of the IBM z/OS core collection version, its c
https://github.com/IBM/ibm_zosmf/blob/main/CHANGELOG.rst#v160
.. _1.5.x changelogs:
https://github.com/IBM/ibm_zosmf/blob/main/CHANGELOG.rst#v150
.. _1.4.x changelogs:
https://github.com/IBM/ibm_zosmf/blob/main/CHANGELOG.rst#v142
.. _1.3.x changelogs:
https://github.com/IBM/ibm_zosmf/blob/main/CHANGELOG.rst#v130
.. _Full support:
../../../collections_content/collection-life-cycles.html#life-cycle-phase
.. _Maintenance support:
../../../collections_content/collection-life-cycles.html#life-cycle-phase
.. _End of life:
../../../collections_content/collection-life-cycles.html#life-cycle-phase
228 changes: 0 additions & 228 deletions docs/source/release_notes.rst
View file
Open in desktop
Copy link
Copy Markdown
Member

@AKippins AKippins May 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

EOL status should affect visibility and labeling, not historical availability. Release notes are part of the product’s operational record, and removing them breaks traceability, supportability, and upgrade clarity. A better approach would be to retain them with clear EOL labeling or move them to an archived section rather than deleting them.

Original file line number Diff line number Diff line change
Expand Up @@ -57,234 +57,6 @@ Availability
* `Galaxy`_
* `GitHub`_

Version 1.4.2
=============

Notes
-----

* The README has been updated with a new template.
* Fixed role `zmf_workflow_complete` which previously failed to return final_result.

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Version 1.4.1
=============

Notes
-----

* Documentation updates
* Fixed ansible-lint issues

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Version 1.4.0
=============

Notes
-----

* Added a new z/OSMF Management Services Catalog role `zmf_zmsc_run_management_service`_ to run a z/OS management service
published in B(z/OS Management Services Catalog).
* Updated module `zmf_workflow` to return the failed step if the workflow is not completed.

* New roles

* `zmf_zmsc_run_management_service`_

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Reference
---------

* The new z/OS Management Services Catalog role `zmf_zmsc_run_management_service`_ works with z/OSMF V2R4
and above with the APAR PH52813 installed.

Version 1.3.0
=============

Notes
-----

* Added a new z/OSMF Software Management role `zmf_swmgmt_identify_missing_critical_updates`_ to determine if a software
instance is missing software updates to resolve PE PTFs, HIPER fixes, or other exception SYSMODs identified by ERROR
HOLDDATA. It also helps you identify the SYSMODs that resolve those exceptions.
* Added a new z/OSMF Software Management role `zmf_swmgmt_identify_missing_fixcat_updates`_ to determine if a software
instance is missing updates for fix categories that might be applicable to the software instance. It also helps you
identify the SYSMODs that resolve the missing updates.
* Added a new z/OSMF Software Management role `zmf_swmgmt_search_software_updates`_ to search a software instance for one
or more software updates to determine which updates are installed or updates that need to be installed.

* New roles

* `zmf_swmgmt_identify_missing_critical_updates`_
* `zmf_swmgmt_identify_missing_fixcat_updates`_
* `zmf_swmgmt_search_software_updates`_

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Reference
---------

* The new software management roles only work with z/OSMF V2R5 and above with the APAR PH47050 installed.
* The new software management roles require proper input values and users who will use these roles should be provided
appropriate access on z/OS system.

Version 1.2.1
=============

Notes
-----

* Removed dependency on Requests library for Python on the control node.

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Version 1.2.0
=============

Notes
-----

* Updated module `zmf_sca`_ for SAF based z/OS security automation, which adds support for provisioning security requirements.
* The updated module `zmf_sca`_ is based on the REST API of the z/OSMF Security Configuration Assistant (SCA) with APAR PH47746.
SCA supports the json format of the security descriptor file. This file can be used to document security requirements
by function or by product. With the security descriptor file that is easy to create,
SCA is able to display and automatically provision security requirements in a flexible granularity,
either by individual requirement, by function or by product. SCA is based on the SAF interface,
therefore it supports all SAF based security products in most cases. To learn more about z/OSMF SCA, please refer to
`SCA blog`_ and the `SCA demo`_ in IBM MediaCenter.

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Reference
---------

* The updated module `zmf_sca`_ requires that z/OSMF SCA is configured properly.
For the required configuration of z/OSMF SCA, please refer to `z/OSMF SCA Configuration`_
* The updated module `zmf_sca`_ only works with z/OSMF V2R4 and above with the APAR PH47746 installed.

Version 1.1.0
=============

Notes
-----

* Added a new module `zmf_sca`_ for SAF based z/OS security automation, which starts with the security validation.
* The new module `zmf_sca`_ is based on the REST API of the z/OSMF Security Configuration Assistant (SCA).
SCA supports the json format of the security descriptor file. This file can be used to document security requirements
by function or by product. With the security descriptor file that is easy to create,
SCA is able to display and automatically validate security requirements in a flexible granularity,
either by individual requirement, by function or by product. SCA is based on the SAF interface,
therefore it supports all SAF based security products in most cases. To learn more about z/OSMF SCA, please refer to
`SCA blog`_ and the `SCA demo`_ in IBM MediaCenter.
* The new module `zmf_sca`_ can be used in use cases like security validation, security audit, etc.
* Added a new cloud provisioning and management (CP&M) role `zmf_cpm_list_software_templates`_ to obtain list of published
software templates that can be provisioned by user who is requesting to obtain the list.
List of templates is saved in a file system and contains detailed information about each software template.
* Added a new CP&M role `zmf_cpm_create_software_instance`_ to create a software
instance in z/OSMF CP&M software instance registry. A json file with various properties for the instance can
be provided to save instance specific properties in the registry.
* Added a new CP&M role `zmf_cpm_get_software_instance`_ to obtain a specific software instance from the z/OSMF CP&M
software instance registry. Retrieved software instance along with associated properties is saved in a file system.

* New modules

* `zmf_sca`_

* New roles

* `zmf_cpm_list_software_templates`_
* `zmf_cpm_create_software_instance`_
* `zmf_cpm_get_software_instance`_

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Reference
---------

* The new module `zmf_sca`_ requires that z/OSMF SCA is configured properly.
For the required configuration of z/OSMF SCA, please refer to `z/OSMF SCA Configuration`_
* The new module `zmf_sca`_ only works with z/OSMF V2R4 and above with the APAR PH41248 installed.
* The new cloud provisioning and management roles requires z/OSMF cloud provisioning and management
configured properly and users who will use these roles should be provided appropriate access on
z/OS system.

Version 1.0.1
=============

Notes
-----

* Initial release of IBM z/OS Management Facility (z/OSMF) collection,
referred to as ibm_zosmf, which is part of the broader offering
Red Hat® Ansible Certified Content for IBM Z.
* Generic documentation is available at the `documentation site`_, covering
guidance on installation, modules, roles and other references.
* Sample playbooks are available at the `samples repository`_.
Each playbook contains a README file that explains which configurations are needed to run a sample playbook.

* New modules

* `zmf_authenticate`_
* `zmf_workflow`_

* New roles

* `zmf_workflow_complete`_
* `zmf_cpm_manage_software_instance`_
* `zmf_cpm_provision_software_service`_
* `zmf_cpm_remove_software_instance`_

Availability
------------

* `Automation Hub`_
* `Galaxy`_
* `GitHub`_

Reference
---------

* Supported by `z/OS V2R3`_ or later.
* Supported by `z/OS Management Facility`_ V2R3 or later.
* Module `zmf_authenticate`_ is supported by z/OSMF APAR PH12143 (PTF UI66511 for V2R3, PTF UI66512 for V2R4).

.. .............................................................................
.. Global Links
Expand Down