Merge "Document the blacklist intent for reviewers."
This commit is contained in:
commit
2854532c85
11
README.rst
11
README.rst
@ -236,6 +236,17 @@ General Review Criteria
|
||||
blueprint requires the new specification. Ideally, changes should
|
||||
already be proposed, so that its use can be seen.
|
||||
|
||||
- The blacklist is for handling dependencies that cannot be constrained.
|
||||
For instance, linters which each project has at a different release level,
|
||||
and which make projects fail on every release (because they add rules) -
|
||||
those cannot be globally constrained unless we coordinate updating all of
|
||||
OpenStack to the new release at the same time - but given the volunteer
|
||||
and loosely coupled nature of the big tent that is infeasible. Dependencies
|
||||
that are only used in unconstrained places should not be blacklisted - they
|
||||
may be constrained in future, and there's no harm caused by constraining
|
||||
them today. Entries in the blacklist should have a comment explaining the
|
||||
reason for blacklisting.
|
||||
|
||||
For new Requirements
|
||||
--------------------
|
||||
|
||||
|
@ -1,3 +1,5 @@
|
||||
# linters - each project may hve a different version with loose convergence
|
||||
# over time.
|
||||
flake8
|
||||
flake8_docstrings
|
||||
hacking
|
||||
@ -6,4 +8,5 @@ pep257
|
||||
pep8
|
||||
pyflakes
|
||||
pylint
|
||||
# release changelog generator - xxx - under discussion
|
||||
reno
|
||||
|
Loading…
Reference in New Issue
Block a user