openstack/project-config
Code Issues Proposed changes

Start including team as release meta field

Browse Source 
This will gives us a reference point so we can start pinging the
relevant people, be that through contacting the release liaison directly
or simply the project's IRC channel.

Change-Id: I4b9cfe2eb785a05d3a5f6ba4a5760f6b6effa6db
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This commit is contained in:
Stephen Finucane 2024-09-19 12:12:36 +01:00 committed by Stephen Finucane
parent 963bb0e3d1
commit 75abedd068
3 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
roles/copy-release-tools-scripts/files/release-tools/README.rst
View File

@ -41,11 +41,12 @@ Example:
::
./release.sh openstack/oslo.rootwrap mitaka 3.0.3 gerrit/master
./release.sh openstack/oslo.rootwrap mitaka 3.0.3 oslo gerrit/master
Apply a 3.0.3 tag (associated to the mitaka series) to the gerrit master
HEAD of the openstack/oslo.rootwrap reporitory, and add a comment for each
closed bug mentioned in commit messages since the previous mitaka tag (3.0.2).
HEAD of the openstack/oslo.rootwrap repository, add a comment for each closed
bug mentioned in commit messages since the previous mitaka tag (3.0.2), and
associate it with the deliverable's team.
branch_from_yaml.sh
===================

7
roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py
View File

@ -60,12 +60,12 @@ def find_modified_deliverable_files(reporoot):
return filenames
def tag_release(repo, series_name, version, diff_start, hash,
def tag_release(repo, series_name, version, team, diff_start, hash,
include_pypi_link, first_full_release, meta_data, branch_name):
print('Tagging {} in {}'.format(version, repo))
try:
subprocess.check_call(
[RELEASE_SCRIPT, repo, series_name, version,
[RELEASE_SCRIPT, repo, series_name, version, team,
diff_start, hash, include_pypi_link,
first_full_release, meta_data, branch_name]
)
@ -196,6 +196,7 @@ def process_release_requests(reporoot, filenames, meta_data):
include_pypi_link = 'yes' if include_pypi_link else 'no'
if deliverable_releases:
team = deliverable_data['team']
all_versions = {
rel['version']: rel for rel in deliverable_data['releases']
}
@ -215,7 +216,7 @@ def process_release_requests(reporoot, filenames, meta_data):
# Tag releases.
for project in this_version['projects']:
error_count += tag_release(
project['repo'], series_name, version,
project['repo'], series_name, version, team,
diff_start, project['hash'], include_pypi_link,
first_full_release, meta_data, branch_name,
)

20
roles/copy-release-tools-scripts/files/release-tools/release.sh
View File

@ -24,12 +24,12 @@ TOOLSDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
source $TOOLSDIR/functions
function usage {
echo "Usage: release.sh [-a] repository series version diff_start SHA include_pypi first-full-release extra-metadata"
echo "Usage: release.sh [-a] repository series version team diff_start SHA include_pypi first-full-release extra-metadata"
echo
echo "Example: release.sh openstack/oslo.rootwrap mitaka 3.0.3 '' gerrit/master yes no 'meta:release:Workflow+1: Doug Hellmann <doug@doughellmann.com>'"
echo "Example: release.sh openstack/oslo.rootwrap mitaka 3.0.3 oslo '' gerrit/master yes no oslo 'meta:release:Workflow+1: Doug Hellmann <doug@doughellmann.com>'"
}
if [ $# -lt 5 ]; then
if [ $# -lt 6 ]; then
usage
exit 2
fi
@ -37,12 +37,13 @@ fi
REPO=$1
SERIES=$2
VERSION=$3
DIFF_START=$4
SHA=$5
INCLUDE_PYPI=${6:-no}
FIRST_FULL=${7:-no}
EXTRA_METADATA="$8"
BRANCH="${9:-master}"
TEAM=$4
DIFF_START=$5
SHA=$6
INCLUDE_PYPI=${7:-no}
FIRST_FULL=${8:-no}
EXTRA_METADATA="$9"
BRANCH="${10:-master}"
SHORTNAME=`basename $REPO`
@ -76,6 +77,7 @@ else
TAGMSG="$SHORTNAME $VERSION $RELEASETYPE
meta:version: $VERSION
meta:team: $TEAM
meta:diff-start: $DIFF_START
meta:series: $SERIES
meta:branch: $BRANCH