The safety run for development should be allowed to fail, while the safety run for install should be required to succeed. This lowers the frequency of safety updates without compromising the installable package.

See zhmcclient/python-zhmcclient#1370 for how it was done in the zhmcclient package.

For details, see zhmcclient/python-zhmcclient#1396

The safety runs had already been split in an earlier PR between "install" and "all". However, the requirements.txt file is now used for install, and that causes safety to pass even when the minimum version has a safety issue. It would only fail is there was a pinning to a version that has safety issues.

This ticket is to improve that by moving the direct and indirect install dependencies in the minimum-constraints.txt file into a new minimum-constraints-install.txt file for use by the safety run for install. The new file would be includes with -c in the existing file.

It seems that the RST formatting of Github has changed, so that the badges in the README.rst page are now displayed vertically instead of horizontally.

Removing the empty lines between the statements in the RST file is not sufficient to solve the problem - we need to change the format of the readme page to MarkDown.

Some of the copyright statements specify a range of years, e.g. "Copyright 2016-2020 ...".

The copyright is claimed automatically for all following years, so only the oldest year needs to be mentioned. It is in fact important to claim the oldest year in any copyright dispute.

If significant changes are made in a particular year, that year can optionally be listed, but the years then must be separated by comma.

This ticket is to change all copyright statements that specify a range of years, to use comma instead of hyphen (assuming that the second year was somehow significant enough to be mentioned).

The following command can be used to list all copyright statements with a year range:

grep -i "Copyright .*20..-20.." . -r

See PR zhmcclient/zhmc-ansible-modules#879 for how this was done in the zhmc ansible project.

Seen on A224 HMC.

Add a new make target 'authors' that generates an AUTHORS.md file from the git commit history.
Add the invocation of 'make authors' to the description of how to release a version in the development documentation.

See zhmcclient/zhmc-ansible-modules#880 for how this was done in the zhmc ansible project.

For details, see zhmcclient/python-zhmcclient#1489

Currently:

• ./docs/usage.rst: TODO: Clarify which ports need to be open
• ./docs/usage.rst:* Object access permission to TODO: Document required object access permissons
• ./docs/usage.rst:* Task permission for TODO: Document required task permissons

Currently, restarting the forwarder will send again all OS messages the HMC has buffered.

This needs to be improved such that the forwarder is aware of the last message sent for each partition. Since this data needs to survive a forwarder restart, it needs to be persisted in the file system.

Python 3.12 has been released on October 2, 2023

• Add to Actions test workflow (in the normal set of environments, replacing 3.11)
• Add to tox.ini
• Add to supported Python versions in Trove classifiers in setup.py

Use "python -m" to call it, since otherwise the wrong packages are reported.

See PR zhmcclient/zhmc-ansible-modules#882 for how this was done in the zhmc ansible project.

• For docker, no port mapping should be needed since they are all outgoing connections (verify)
• List formatting issue in usage.html#hmc-userid-requirements
• Currently, no version-specific docs is created on RTD, but the change log link on the release page references the version-specific docs.

Reasons:

• Python 3.5 support has officially ended 2020-09-05 with the release of 3.5.10
• Less safety issues to be resolved
• Simplifies dependencies and minimum constraints a lot
• Allows to get rid of old versions of all kinds of packages
• Less test runs in full tests run weekly and for releases, and also to some extent in PR-level runs
• We use a very outdated Pylint version 2.5 on Python 3.5
• We do not run the safety command on Python 3.5