Open Stack

On 10/3/2018 11:21 AM, Zane Bitter wrote:
>>> That patch is the only thing blocking the cleanup patch in
>>> project-config, so I would like to get a definitive answer about what to
>>> do. Should we close the branch, or does someone want to try to fix
>>> things up?
> 
> I think we agreed on closing the branch, and Rico was looking into the 
> procedure for how to actually do that.
> 
>>> Doug
>>>
>>> [1]https://review.openstack.org/#/c/597272/
>>
>> I'm assuming heat-agents is a service, not a library, since it doesn't 
>> show up in upper-constraints.
> 
> It's a guest agent, so neither :)
> 
>> Based on that, does heat itself plan on putting its stable/ocata 
>> branch into extended maintenance mode and if 
> 
> Wearing my Red Hat hat, I would be happy to EOL it. But wearing my 
> upstream hat, I'm happy to keep maintaining it, and I was not proposing 
> that we EOL heat's stable/ocata as well.
> 
>> so, does that mean EOLing the heat-agents stable/ocata branch could 
>> cause problems for the heat stable/ocata branch? In other words, will 
>> it be reasonable to run CI for stable/ocata heat changes against a 
>> heat-agents ocata-eol tag?
> 
> I don't think that's a problem. The guest agents rarely change, and I 
> don't think there's ever been a patch backported by 4 releases.

OK, cool, sounds like killing the heat-agent ocata branch is the thing 
to do then.

-- 

Thanks,

Matt