68f7c558b9
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> |
||
---|---|---|
.. | ||
__init__.py | ||
check_diff_start.py | ||
check_schema.py | ||
edit_deliverable.py | ||
find_gerrit_acl_issues.py | ||
get_deliverable_owner.py | ||
init_series.py | ||
interactive_release.py | ||
list_changes.py | ||
list_constraints.py | ||
list_deliverables.py | ||
mail.py | ||
make_tracking_pad.py | ||
missing.py | ||
new_release.py | ||
propose_final_releases.py | ||
propose_library_branches.py | ||
reformat_yaml.py | ||
release_notes.py | ||
validate.py |