Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.2

[Ihar Hrachyshka]

Tony Breeds <t...@bakeyournoodle.com> wrote:

On Thu, Sep 08, 2016 at 09:21:57AM -0500, Matthew Thode wrote:

Ya that makes sense, the patch can be altered to just block 4.13.1,2
(assuming 4.13.3 really does fix it)

I feel like we've gotten ourselves (well at least I'm confused) about what
we're trying to achieve here.


for everyone both requirements consumers and non-consumers.

That seems to be done by:
1. Release oslo.db (4.13.3)
    https://review.openstack.org/#/c/367482/
2. Bump upper-constraints to point to the new release
    Generated once the review above merges
    Once it is generated we can abandon: 
https://review.openstack.org/#/c/366298/
4. Update global-requirements to mark some oslo.db versions as bad
    I'll update https://review.openstack.org/#/c/365565 RSN

It seem to be the primary purpose is to get a release of oslo.db out that works

Agreed. Though I already have a patch for that: https://review.openstack.org/#/c/365565/

5. Re-Release library packages that get a new the restricted oslo.db
   requirement.


and upper-constraints.txt


even then it's a risky change at this stage.

There is also another goal to unblock PyMysql 0.7.7 from global-requirements I don't see the need for this. If distros were shipping 0.7.7 then maybe but

Agreed, and I expressed the same sentiment in Matthew’s patches before.

https://packages.gentoo.org/packages/dev-python/pymysql
https://build.opensuse.org/package/show/devel:languages:python/python-PyMySQL
https://launchpad.net/ubuntu/+source/python-pymysql
https://apps.fedoraproject.org/packages/python-PyMySQL
http://ftp.redhat.com/redhat/linux/enterprise/7Server/en/RHOS/SRPMS/python-PyMySQL-0.6.7-2.2.el7ost.src.rpm


distro packagers will know to skip it.

We should Abandon https://review.openstack.org/#/c/364541/

The only really compelling reason for unblocking 0.7.7 *now* would be because we can't do it after we branch[1] but if we leave it masked it just means that

Agreed, except that I don’t suggest we should abandon it. If there is some interest in unblocking it, then just postpone it to when Ocata is open.

signature.asc
Description: Message signed with OpenPGP using GPGMail

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev