Prefer to use tox env venv rather than command with tox path

Using tox -e venv directly allow us to remove the dedicated note.

Change-Id: I2db41dbcd2989a4b3953f3396b7f11ecd34712f2
This commit is contained in:
Hervé Beraud 2020-05-06 14:16:22 +02:00
parent ec8c81fb07
commit 8e31919d02
1 changed files with 3 additions and 6 deletions

View File

@ -52,11 +52,8 @@ When making releases, there are some useful commands to know. First, to find
all the changes in all the Oslo libraries since they were last released, use
the following commands in the openstack/releases repo::
./tools/list_unreleased_changes.sh master $(.tox/venv/bin/list-deliverables --team oslo -r)
./tools/list_unreleased_changes.sh master $(.tox/venv/bin/list-deliverables --team oslo -r --series independent)
.. note:: These commands assume that the ``venv`` tox environment has been
created. That can be done with the command ``tox -e venv --notest``
./tools/list_unreleased_changes.sh master $(tox -e venv -- list-deliverables --team oslo -r)
./tools/list_unreleased_changes.sh master $(tox -e venv -- list-deliverables --team oslo -r --series independent)
.. note:: Oslo contains both libraries that are tied to the OpenStack release
as well as some that are independent of it. That's why two commands
@ -65,7 +62,7 @@ the following commands in the openstack/releases repo::
To do the same for a stable branch, use the following (replace the branch names
as appropriate)::
./tools/list_unreleased_changes.sh stable/train $(.tox/venv/bin/list-deliverables --team oslo -r --series train)
./tools/list_unreleased_changes.sh stable/train $(tox -e venv -- list-deliverables --team oslo -r --series train)
Meetings
--------