These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements.
The default precommit Dockerfile now relies on pip to grab an up-to-date version of pylint, rather than rely on the version shipped in dpkg.
This changes various verify_ functions such that 0 is always yes/true and 1 is always no/false. This should make it easier/more obvious what test is being performed in if statements. Be aware that this will likely break any personalities or plug-ins that were written against previous versions.
Releasedocmaker now supports sorting issues based either on resolution date or issue id. The default remains the same: release date in oldest-first order.
See the docs for more information.
Users of release doc maker can now specify which lint checks they would like used via the
--lint command line arguement. Available options are:
incompatible- issues flagged incompatible should have release notes
important- issues marked important should have release notes
version- issues should have a version string of the form major.minor.other or description-_revision
component- issues should specify a component
assignee- issues should have an assignee
all- all of the above
For backwards compatibility, the
releasedocmaker wrapper script included in the Yetus convenience binary will treat a bare
--lint argument as
--lint=all. Users that directly invoke the
releasedocmaker.py python script will have to update their invocation.
This patch adds the qbt (
quality build tool) command in order to run test-patch as a regularly scheduled reporting tool against a source tree without the necessity of providing a patch file.
This feature has changed several internal structures and control mechanisms to be incompatible with previous releases:
docker runcommand. Now this is done via the
BINNAMEnow strips off the .sh extension.
PATCH_OR_ISSUEand related vars may be empty when running in the full build mode.