From: Lott, Christopher (cl778h) Date: Sat, 16 Nov 2019 11:28:28 +0000 (-0500) Subject: Remove passive voice in python, release job RST X-Git-Url: https://gerrit.linuxfoundation.org/infra/gitweb?a=commitdiff_plain;h=e1a8dc64cfe10360ebdcadd28806adf800760ce7;p=releng%2Fglobal-jjb.git Remove passive voice in python, release job RST Change-Id: Ie20a255c670a87a6e95e2c3c5c11bcf6b2c91097 Signed-off-by: Lott, Christopher (cl778h) (cherry picked from commit d6e0198a565eff38a881d8b7c9f629764d7c2c24) --- diff --git a/docs/jjb/lf-python-jobs.rst b/docs/jjb/lf-python-jobs.rst index 3b142647..ca309d67 100644 --- a/docs/jjb/lf-python-jobs.rst +++ b/docs/jjb/lf-python-jobs.rst @@ -361,13 +361,13 @@ pyenv variables before running. export PYENV_ROOT="/opt/pyenv" export PATH="$PYENV_ROOT/bin:$PATH" -Installable package projects should consider using a directory layout -like the one shown below. All Python files are below a directory, and -the package source files are nested in a subdirectory. This layout -allows straightforward build-job triggers using the directory paths so -Jenkins jobs are triggered appropriately. For example, a PyPI merge -job should not be triggered by a non-Python change, because the job -cannot upload the same package twice. +Installable package projects should use the directory layout shown +below. All Python files are in a repo subdirectory separate from +non-Python files like documentation. This layout allows highly +specific build-job triggers in Jenkins using the subdirectory +paths. For example, a PyPI merge job should not run on a non-Python +file change such as documentation, because the job cannot upload the +same package twice. .. code-block:: bash diff --git a/docs/jjb/lf-release-jobs.rst b/docs/jjb/lf-release-jobs.rst index e124f8cf..77b46d19 100644 --- a/docs/jjb/lf-release-jobs.rst +++ b/docs/jjb/lf-release-jobs.rst @@ -208,7 +208,7 @@ packages. release repositories, for example "mypackage". :python_version: The Python interpreter version to use for pip "Requires-Python" compatibility checks, for example '3', '3.7' or 3.7.4. - Valid decimal values such as 3 and 3.7 must be quoted. + Put valid decimal values such as 3 or 3.7 in quotes to pass schema validation. :version: The semantic version string used for the package in the setup.py file.