Re: [openstack-dev] [neutron] constrained tox targets

2016-03-07 Thread Armando M.
On 4 March 2016 at 11:15, Armando M. wrote: > > > On 4 March 2016 at 11:12, Ihar Hrachyshka wrote: > >> Armando M. wrote: >> >> >>> >>> On 4 March 2016 at 08:50, Ihar Hrachyshka wrote: >>> Hi all, >>> >>>

Re: [openstack-dev] [neutron] constrained tox targets

2016-03-04 Thread Armando M.
On 4 March 2016 at 11:12, Ihar Hrachyshka wrote: > Armando M. wrote: > > >> >> On 4 March 2016 at 08:50, Ihar Hrachyshka wrote: >> Hi all, >> >> currently we have both py27 and py27-constraints tox targets in neutron >> repos. For

Re: [openstack-dev] [neutron] constrained tox targets

2016-03-04 Thread Ihar Hrachyshka
Armando M. wrote: On 4 March 2016 at 08:50, Ihar Hrachyshka wrote: Hi all, currently we have both py27 and py27-constraints tox targets in neutron repos. For some repos (neutron) they are even executed in both master and stable/liberty gates. TC

Re: [openstack-dev] [neutron] constrained tox targets

2016-03-04 Thread Armando M.
On 4 March 2016 at 08:50, Ihar Hrachyshka wrote: > Hi all, > > currently we have both py27 and py27-constraints tox targets in neutron > repos. For some repos (neutron) they are even executed in both master and > stable/liberty gates. TC lately decided that instead of having

[openstack-dev] [neutron] constrained tox targets

2016-03-04 Thread Ihar Hrachyshka
Hi all, currently we have both py27 and py27-constraints tox targets in neutron repos. For some repos (neutron) they are even executed in both master and stable/liberty gates. TC lately decided that instead of having separate targets for constrained requirements, we want to have