Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Doug Hellmann
Excerpts from Mike Bayer's message of 2017-03-15 12:39:48 -0400: > > On 03/15/2017 11:42 AM, Sean Dague wrote: > > Perhaps, but in doing so oslo.db is going to get the pin and uc from > > stable/ocata, which is going to force it back to SQLA < 1.1, which will > > prevent oslo.db changes that

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Mike Bayer
On 03/15/2017 11:42 AM, Sean Dague wrote: Perhaps, but in doing so oslo.db is going to get the pin and uc from stable/ocata, which is going to force it back to SQLA < 1.1, which will prevent oslo.db changes that require >= 1.1 to work. so do we want to make that job non-voting or

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Sean Dague
Perhaps, but in doing so oslo.db is going to get the pin and uc from stable/ocata, which is going to force it back to SQLA < 1.1, which will prevent oslo.db changes that require >= 1.1 to work. -Sean On 03/15/2017 11:26 AM, Roman Podoliaka wrote: > Isn't the purpose of that specific job

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Roman Podoliaka
Isn't the purpose of that specific job - gate-tempest-dsvm-neutron-src-oslo.db-ubuntu-xenial-ocata - to test a change to the library master branch with stable releases (i.e. Ocata) - of all other components? On Wed, Mar 15, 2017 at 5:20 PM, Sean Dague wrote: > On 03/15/2017 10:38

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Sean Dague
On 03/15/2017 10:38 AM, Mike Bayer wrote: > > > On 03/15/2017 07:30 AM, Sean Dague wrote: >> >> The problem was the original patch kept a cap on SQLA, just moved it up >> to the next pre-release, not realizing the caps in general are the >> concern by the requirements team. So instead of upping

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Mike Bayer
On 03/15/2017 07:30 AM, Sean Dague wrote: The problem was the original patch kept a cap on SQLA, just moved it up to the next pre-release, not realizing the caps in general are the concern by the requirements team. So instead of upping the cap, I just removed it entirely. (It also didn't help

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Sean Dague
On 03/15/2017 05:32 AM, Thierry Carrez wrote: > Mike Bayer wrote: >> As mentioned previously, SQLAlchemy 1.1 has now been released for about >> six months. My work now is on SQLAlchemy 1.2 which should hopefully >> see initial releases in late spring.SQLAlchemy 1.1 includes tons of >>

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-15 Thread Thierry Carrez
Mike Bayer wrote: > As mentioned previously, SQLAlchemy 1.1 has now been released for about > six months. My work now is on SQLAlchemy 1.2 which should hopefully > see initial releases in late spring.SQLAlchemy 1.1 includes tons of > features, bugfixes, and improvements, and in particular

[openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

2017-03-14 Thread Mike Bayer
Hello all - As mentioned previously, SQLAlchemy 1.1 has now been released for about six months. My work now is on SQLAlchemy 1.2 which should hopefully see initial releases in late spring.SQLAlchemy 1.1 includes tons of features, bugfixes, and improvements, and in particular the most