openstack/rally
Code Issues Proposed changes

Propose rally 3.4.0 release

Browse Source 
Change-Id: I2463227b1d4a114c0c5caa093f72b5b0b7c50d4e
This commit is contained in:
Andrey Kurilin
2023-05-19 23:31:59 +02:00
parent b4d31cf8cf
commit e8613ffeb0
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.rst
View File

@@ -17,8 +17,8 @@ Changelog
.. Release notes for existing releases are MUTABLE! If there is something that .. Release notes for existing releases are MUTABLE! If there is something that
was missed or can be improved, feel free to change it! was missed or can be improved, feel free to change it!
[unreleased] [3.4.0] - 2023-05-23
------------ --------------------
This is the last release with support of Python 3.6 and Python 3.7 This is the last release with support of Python 3.6 and Python 3.7

8
DOCKER_README.md
View File

@@ -17,7 +17,7 @@ additional plugins:
# for rally user is used. # for rally user is used.
# #
# Tags of the image are the same as releases of xRally/Rally # Tags of the image are the same as releases of xRally/Rally
FROM xrally/xrally:3.3.0 FROM xrally/xrally:3.4.0
# "rally" user (which is selected by-default) is owner of "/rally" directory, # "rally" user (which is selected by-default) is owner of "/rally" directory,
# so there is no need to call chown or switch the user # so there is no need to call chown or switch the user
@@ -40,8 +40,8 @@ details)
First, you need to pull the container. We suggest using the last tagged First, you need to pull the container. We suggest using the last tagged
version: version:
# pull the 3.3.0 image (the latest release at the point of writing the note) # pull the 3.4.0 image (the latest release at the point of writing the note)
$ docker pull xrally/xrally:3.3.0 $ docker pull xrally/xrally:3.4.0
**WARNING: never attach folders and volumes to `/rally` inside the container. It can break everything.** **WARNING: never attach folders and volumes to `/rally` inside the container. It can break everything.**
@@ -57,7 +57,7 @@ docker volumes or mount the directory.
* use docker volumes. It is the easiest way. You just need to do something like: * use docker volumes. It is the easiest way. You just need to do something like:
$ docker volume create --name rally_volume $ docker volume create --name rally_volume
$ docker run -v rally_volume:/home/rally/.rally xrally/xrally:3.3.0 env create --name "foo" $ docker run -v rally_volume:/home/rally/.rally xrally/xrally:3.4.0 env create --name "foo"
* mount outer directory inside the container * mount outer directory inside the container