Markus Hilger
5311437d0e
Every rule added here is at zero once the previous commit lands, so it costs no cleanup: the point is that a future patch cannot introduce one without the ruff job failing. They are the rest of pyflakes' format-string checks, flake8-2020, most of bugbear, the pylint warnings that describe bugs rather than style, four flake8-async rules for blocking calls in coroutines, and some RUF, LOG, PGH, PIE, ISC and EXE rules in the same spirit. Each was confirmed to fire on a synthetic violation, so none is silently inert under the py37 target. Rules are named by group wherever the group is already clean, and each prefix stops short of a rule that is not: PLW150 rather than PLW15, which would pull in PLW1510. Bugbear is listed rule by rule apart from B02 and B03, since B006, B007 and B018 are all left out on purpose.
Confluent
Confluent is a software package to handle essential bootstrap and operation of scale-out server configurations. It supports stateful and stateless deployments for various operating systems.
Check this page for a more detailed list of features.
Confluent is the modern successor of xCAT. If you're coming from xCAT, check out this comparison.
Documentation
Confluent documentation is hosted on: https://xcat2.github.io/confluent-docs/
Download
Get the latest version from: https://xcat2.github.io/confluent-docs/downloads/
Check release notes on: https://xcat2.github.io/confluent-docs/release_notes/
Open Source License
Confluent is made available under the Apache 2.0 license: https://opensource.org/license/apache-2-0
Developers
Want to help? Submit a Pull Request.
Versioning and releases
The top-level VERSION file names the release the current branch is working toward. Build scripts
call ./mkversion, which turns it into the version stamped on packages: the tag itself on a release
tag (4.0.1), otherwise a development version (4.0.1.dev5+gdeadbee, or 4.0.1~dev5+gdeadbee for
the packages that have no setup.py).
mkversion also derives a version from the newest tag reachable from HEAD and uses whichever is
higher, so forgetting to bump VERSION after tagging the current branch cannot walk the version
backwards. Staying ahead of tags on other branches is what VERSION itself is for: patch releases
are tagged on release branches, which master never sees.
Cutting a new series:
- Land the release commit on master and tag
X.Y.0there. - Create branch
X.Yfrom that tag; it inheritsVERSION=X.Y.0. - Only then bump
VERSIONon master. Doing it before step 2 leaves the release branch on the wrong series.
Patch releases land on branch X.Y and are tagged X.Y.Z there; no VERSION edit is needed.