summaryrefslogtreecommitdiff
path: root/releasenotes/notes/change-dist-name-288024b5d6668c01.yaml
diff options
context:
space:
mode:
authorDoug Hellmann <doug@doughellmann.com>2018-09-28 14:22:24 -0400
committerMatthew Thode <mthode@mthode.org>2019-04-05 21:24:36 -0500
commit1240c5cedac70c06f449a83ccb00bbf23c6884b2 (patch)
tree3cd13473fbe6a8a757f810ab1bb68cf53b00cc86 /releasenotes/notes/change-dist-name-288024b5d6668c01.yaml
parent32510405788c57eb0ffeededd927239dcce3cd81 (diff)
downloadheat-1240c5cedac70c06f449a83ccb00bbf23c6884b2.tar.gz
change the dist name to 'openstack-heat'
We are updating all Python projects to publish artifacts to PyPI. The name "heat" is already taken there by another project, and they have rejected our request to claim the name. We therefore need to change the dist name used to package heat. We have some other projects publishing using an "openstack-" prefix, so I propose using the name "openstack-heat". This will not change the imports or anything else about how the code works, just how it is packaged. Add a grenade plugin for upgrading between the packages with different names so that we can clean up the old version of the code and avoid discovering the heat plugins multiple times in different locations. Change-Id: I59b55cffd9e648f842eb286b936f09c5b55a76db Signed-off-by: Doug Hellmann <doug@doughellmann.com> (cherry picked from commit 8ae5f8657b2bdf841bdf114b49839700c2ee924f)
Diffstat (limited to 'releasenotes/notes/change-dist-name-288024b5d6668c01.yaml')
-rw-r--r--releasenotes/notes/change-dist-name-288024b5d6668c01.yaml7
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/change-dist-name-288024b5d6668c01.yaml b/releasenotes/notes/change-dist-name-288024b5d6668c01.yaml
new file mode 100644
index 000000000..8925ce369
--- /dev/null
+++ b/releasenotes/notes/change-dist-name-288024b5d6668c01.yaml
@@ -0,0 +1,7 @@
+---
+upgrade:
+ - |
+ The distribution name has been changed from "heat" to
+ "openstack-heat" so that we can publish packages to pypi.org. This
+ may have an effect on downstream package builds if they rely on
+ asking setuptools to determine the package name.