openstack/releases
Code Issues Proposed changes

new-release: Drop tarball-base from individual releases

Browse Source 
We now track explicit tarball base names at a top level under
repository-settings instead of per release. The only time it should be
needed per release is if a project changes their package name part way
through the cycle.

Since most teams are now publishing to pypi and have worked through
needing to rename their packages, it should be safe to update
new-release to not include the tarball-base override per individual
project in a release.

Change-Id: If1c77e358b48113a7fb4d7a48ed8d31841ab9419
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2019-09-11 10:45:26 -05:00
parent 30172de8b0
commit 68f7c558b9
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
openstack_releases/cmds/new_release.py
View File

@ -423,9 +423,6 @@ def main():
if found:
break
repo_info = deliverable_info['repository-settings'][repo]
tarball_base = repo_info.get('tarball-base')
if is_retagging or (
is_em and deliverable_info['release-model'] != 'untagged'):
# Always use the last tagged hash, which should be coming
@ -456,8 +453,6 @@ def main():
'hash': sha,
'comment': comment,
}
if tarball_base:
new_project['tarball-base'] = tarball_base
projects.append(new_project)
elif is_eol or is_em:
@ -470,8 +465,6 @@ def main():
'repo': repo,
'hash': sha,
}
if tarball_base:
new_project['tarball-base'] = tarball_base
projects.append(new_project)
elif previous_sha != sha or force_tag:
@ -482,8 +475,6 @@ def main():
'repo': repo,
'hash': sha,
}
if tarball_base:
new_project['tarball-base'] = tarball_base
projects.append(new_project)
else: