Bump version to 0.11.0

[zhukovgreen]

Packaging

• Bump leapp-framework capability to 1.3

Framework

Fixes

• Preserve verbose/debug options during the whole upgrade workflow (Fix handling of debug/verbose in {pre,}upgrade #625)
• Print the informative error block to the STDOUT instead of STDERR (Fix output location for errors block #623)

Enhancements

• Added new reporting tags: PUBLIC_CLOUD and RHUI (Add new tags #650)
• Added the possibility to skip actor discovery to improve performance of tests when an actor context is injected directly (Feature/skip actors discovery option #638)
• Introduced the deprecated and suppress_deprecation decorators to support the deprecation process (Introduction of the @deprecated decorator & integration into the workflow executions #640, Improve deprecation doc #653)
• Store dialog answers in the leapp.db (dialogs: Create audit entries for dialog answers #651)

Known issues

• The suppress_deprecation decorator causes a traceback in certain cases

Leapp

Enhancements

• Updated and improved man pages (Update and reformat manual pages #633)

Snactor

Fixes

• Raising a missing exception with tests failing under py3 (Fix problem when traceback for py3 was lost #647)

Enhancements

• Added the --actor-config option to snactor run to specify a workflow configuration model that should be consumed by actors (Add --actor-config to snactor run #627)

Leapp Standard Library

Enhancements

• The call function has been improved to be working on MacOS (Make stdlib.call work with kqueue #634)

[centos-ci]

Can one of the admins verify this patch?

[leapp-bot]

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the
Leapp Guidelines.

If you want to re-run tests or request review, you can use following commands as a comment:

• leapp-ci build to run unit tests and copr build
• e2e tests to run unit tests, copr build and end-to-end tests (OAMG members only)
• review please to notify leapp developers of review request

Note: In case there are problems with tests hanging or pending for a long time, please consider rerunning the CI by commenting leapp-ci build.

[zhukovgreen]

@oamg/developers @oamg/qe hi all, please help me to make this list of changes comprehensive. Thank you

[zhukovgreen]

ref oamg/leapp-repository#558

[pirat89]

@zhukovgreen Leapp has different structure for changelogs than leapp-repository.

[pirat89]

To preserve original research from @zhukovgreen , it could be used to complete references to PRs (nice to have, but not required):

Unsorted // should go in some following chapters or removed

#634
#635
#633
#641
#645
#650

Packaging

Fixes

• Fix handling of debug/verbose in {pre,}upgrade #625 debug mode was inconsistent before. This is now fixed
• Fix/empty answerfile #632 empty answerfile when running leapp upgrade fixed
• Fix problem when traceback for py3 was lost #647 fixed lost traceback when failing tests running under py3

Enhancements

• Add --actor-config to snactor run #627 added support for specifying a model which the actor should consume for configuration data
• Update and reformat manual pages #633 man pages updated and improved
• Chore/docs/make single landing page #637 single contributors landing page is introduced
• Introduction of the @deprecated decorator & integration into the workflow executions #640 introduced deprecation functionality to support deprecation process Improve deprecation doc #653
• Allow running unit tests as not a root #648 now tests might be executed without the need to be root

Additional changes interesting for devels

[pirat89]

@oamg/developers @vinzenz I am just thinking, is there any incompatibility in comparison to previous version? Are we going with 0.11.0 or 0.10.1? It's just nitpick, we can go with 0.11.0 anyway, but if have still published somewhere doc about our versioning, we should follow it. But I guess we lost it.

@vinzenz If you have time, please create an issue for the decorator we discussed on Monday. Or draft PR, even without tests, just as reference.

[pirat89]

@zhukovgreen actually, template for changelogs could be worthy :)

[pirat89]

Empty section should be dropped in the official changelog.

[pirat89]

Just hint for changelofs: Things that are not part of packages, should not be usually part of release notes.
It's not 'final' golden rule, but in the most cases it works.

E.g. Changes in the upstream documentation are not part of the release. As well, documentation is active all the time and it is not versioned till this day. Man page documentation is different, as it is delivered to customers.

OTOH, if something is part of changelogs and we have good documentation for it, link could be worthy.