This fixes all the warnings emitted by flake8, mostly involving
qualified imports, import grouping, and indentation.
Change-Id: Ia45839f3e65e15a34e2a2793fd21b83e4fc891d7
Needed-By: I158ea10f104549dd4f0f3ff777b39feb5886642e
* update test requirements with what's in g-r
* Remove hard-coded dependencies from tox.ini as update-requirements
does not edit tox.ini
* Remove requirements.txt as it is redundant (sdist already has it)
* Fix up all the issues identified by flake8
Co-Authored-By: Robert Collins <rbtcollins@hp.com>
Change-Id: I0508bd74edda20fbf844e7303c9b44b80ff794ef
New version of spec2bp:
- takes the project and blueprint name as arguments, instead of a file
- supports not-yet-approved specs (use --in-review to set them "Blocked")
- sets series goal as well as milestone targets
- if the BP and approved spec names don't match, you can use --specpath
to specify the spec location
- if --specpath is not provided, but the blueprint URL looks like it
points to a spec document, spec2bp will infer path from that instead
- if milestone or priority are already set, the --milestone and
--priority parameters are optional (current values will be kept if
parameter is omitted)
- spec2bp will recognize projects from the oslo projectgroup and use
oslo-specs for those
Example usage:
Glance's super-spec.rst was approved and you want to add it to juno-2,
with Medium priority:
./spec2bp.py glance super-spec --milestone=juno-2 --priority=Medium
Nova's my-awesome-spec.rst is still under review, but you would like
to add the my-awesome-spec blueprint to juno-2 (marked Blocked). Since
it's located in a non-standard path, we specify it using --specpath
parameter:
./spec2bp.py nova --specpath=specs/kilo/approved/my-awesome-spec.rst
--in-review --milestone=juno-2
my-awesome-spec is now approved. You want to flip all the approval
bits, but also change its priority to High. There is no need to pass
--specpath again, spec2bp will infer it from the blueprint URL field:
./spec2bp.py nova my-awesome-spec --priority=High
Change-Id: Idba1f042ffb836ac782f50d91802b2a6f4ff44c1
The launchpad project and specs repository may have different names,
especially for a project like Oslo with many launchpad projects.
Change-Id: I4091e7719395378978a101e9c905da84080ad371
Oslo projects share a common specs repository, but since we are in a
different Launchpad project group from the rest of OpenStack the URL for
the blueprints generated by default does not match. This change looks
for "oslo" as the project name that we parse from the spec file and
converts it to "oslo-incubator" by default. To handle specs for other
Oslo libraries, a new option is provided to explicitly set the Launchpad
project name.
Change-Id: I27c76b93a55856ef4fac48debf706a4d152a740a
Do not hard-code the python interpreter, so it is possible to run the
command with a virtualenv containing its dependencies.
Change-Id: Ie5f81c120c18ec8f66a62d95d2107e2513445f5c
Add script to automatically set blueprint fields for an accepted spec.
Point it to a file in a -specs git repository, specify the target
milestone and off you go. By default, sets priority to Low:
Example:
spec2bp.py ../oslo-specs/specs/juno/graduate-oslo-i18n.rst juno-3
Change-Id: Ie5118e29deea1b455623117828057fca4cf69415
Jeremy Stanley