[openstack-dev] [blazar][release] we need a new blazar client release

Doug Hellmann doug at doughellmann.com
Fri Jan 26 21:44:30 UTC 2018


Excerpts from Doug Hellmann's message of 2018-01-26 16:41:23 -0500:
> The PyPI service is now validating package metadata more strictly, and
> the classifier values for python-blazarclient do not pass the validation
> checks. This means the 1.0.0 package we built cannot be uploaded to
> PyPI [1].
> 
> The fix will take several steps.
> 
> 1. dmsimard has proposed [2] to master to fix the classifiers.
> 
> 2. However, since the repository has
>    already been branched for queens we will also need to backport
>    that fix to stable/queens.  David has proposed that backport in
>    [3].
> 
> 3. There are 2 other patches in stable/queens that need to be
>    approved as well [4].
> 
> 4. After they are all merged we can release 1.0.1 from the stable/queens
>    branch using the SHA for the merge commit created when [3] lands.
> 
> So, blazar team, please approve all of those patches and then propose a
> new 1.0.1 release quickly.
> 
> Doug
> 
> [1] http://logs.openstack.org/1d/1d46185bf1e0c18f69038adedd37cf6f6eaf06ab/release/release-openstack-python/13aa058/ara/result/26cee65c-b3cd-4267-9a03-1fe45be043d4/
> [2] https://review.openstack.org/538340 Remove commas in setup.cfg package classifiers
> [3] https://review.openstack.org/538343
> [4] https://review.openstack.org/#/q/status:open+project:openstack/python-blazarclient+branch:stable/queens

In order to speed things along, I'm going to go ahead and use my release
manager ACLs to approve those stable branch changes. So please approve
the one on master so your next release there won't have the same issue.

Doug



More information about the OpenStack-dev mailing list