Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On 2017-03-02 09:56:28 -0800 (-0800), Ihar Hrachyshka wrote: > On Thu, Mar 2, 2017 at 8:13 AM, Pavlo Shchelokovskyy > wrote: > > I'm also kind of wondering what the grenade job in stable/newton will test > > after mitaka EOL? upgrade from mitaka-eol tag to

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On Thu, Mar 2, 2017 at 8:13 AM, Pavlo Shchelokovskyy wrote: > I'm also kind of wondering what the grenade job in stable/newton will test > after mitaka EOL? upgrade from mitaka-eol tag to stable/newton branch? Then > even that might be affected if devstack-gate +

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

Hi Dmitry, > I'm not sure why removing of *_ssh drivers from master should > necessary break stable/mitaka, where these drivers are present. Could > you elaborate? My main concern is the following: both project-config and devstack-gate are branch-less. When removing the *_ssh drivers from tree,

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On 03/01/2017 08:19 PM, Jay Faulkner wrote: On Mar 1, 2017, at 11:15 AM, Pavlo Shchelokovskyy wrote: Greetings ironicers, I'd like to discuss the state of the gates in ironic and other related projects for stable/mitaka branch. Today while making some test

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On 03/01/2017 08:15 PM, Pavlo Shchelokovskyy wrote: Greetings ironicers, I'd like to discuss the state of the gates in ironic and other related projects for stable/mitaka branch. Hi! Thanks for raising this. I need to apologize, I haven't been doing great job as a stable liaison recently.

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On Wed, Mar 01, 2017 at 09:29:14PM +, Jeremy Stanley wrote: > On 2017-03-01 13:24:09 -0800 (-0800), Ihar Hrachyshka wrote: > [...] > > Other projects spent some time upfront and adopted constraints > > quite a while ago. I am surprised that there are still stable > > branches that don't do

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On Wed, Mar 01, 2017 at 01:24:09PM -0800, Ihar Hrachyshka wrote: > I am surprised that there are still > stable branches that don't do that. It's so much easier to maintain > them with constraints in place! Taking a tanget. At the begining of the Ocata cycle we only had 55% constraints usage on

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On 2017-03-01 13:24:09 -0800 (-0800), Ihar Hrachyshka wrote: [...] > Other projects spent some time upfront and adopted constraints > quite a while ago. I am surprised that there are still stable > branches that don't do that. [...] Yep, I had to backport it for some oslo.middleware stable

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

Agreed. All I am saying is that as long as there was no change in the policy, projects are expected to keep up. I see that upper-constraints.txt mentioned in the email several times. I believe it's the least that the project could do to fix the branch, and lack of the fix doesn't seem like a good

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On 2017-03-01 11:36:47 -0800 (-0800), Ihar Hrachyshka wrote: > On Wed, Mar 1, 2017 at 11:15 AM, Pavlo Shchelokovskyy > wrote: > > With all the above, the question is should we really fix the gates for the > > mitaka branch now? According to OpenStack release page [1]

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

On Wed, Mar 1, 2017 at 11:15 AM, Pavlo Shchelokovskyy wrote: > With all the above, the question is should we really fix the gates for the > mitaka branch now? According to OpenStack release page [1] the Mitaka > release will reach end-of-life on April 10, 2017. Yes

Re: [openstack-dev] [ironic] state of the stable/mitaka branches

> On Mar 1, 2017, at 11:15 AM, Pavlo Shchelokovskyy > wrote: > > Greetings ironicers, > > I'd like to discuss the state of the gates in ironic and other related > projects for stable/mitaka branch. > > Today while making some test patches to old branches I