[openstack-dev] [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

Takashi Yamamoto yamamoto at midokura.com
Fri Nov 25 14:23:28 UTC 2016


On Fri, Nov 25, 2016 at 8:02 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>
>> On 25 Nov 2016, at 11:02, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>>
>> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>>
>>>> On 25 Nov 2016, at 09:25, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>>>>
>>>> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>>>>
>>>>>> On 25 Nov 2016, at 05:26, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>>>>>>
>>>>>> hi,
>>>>>>
>>>>>> networking-midonet doesn't have stable/newton branch yet.
>>>>>> newton jobs failures are false alarms.
>>>>>>
>>>>>> branching has been delayed because development of some futures
>>>>>> planned for newton has not been completed yet.
>>>>>>
>>>>>> the plan is to revert ocata-specific changes after branching newton.
>>>>>
>>>>> I don’t think it’s a good idea since you will need to tag a release on branch creation, that is supposed to be compatible with next releases in that same branch.
>>>>
>>>> can't we create the tag after the revert?
>>>>
>>>
>>> No, that’s release team requirement that they branch on a release tag.
>>
>> ok, i didn't know the requirement. thank you.
>>
>>>
>>>> anyway no one think this is a good idea.
>>>> it's just an unfortunate compromise we ended up.
>>>> we are trying to make the schedule better for next release.
>>>
>>> It would make more sense to tag on a compatible commit from the past and consider it a first stable release. (Of course it means that feature development would need to be aligned appropriately.)
>>
>> in that case, can we backport the features?
>> (namely qos and lbaas drivers are in my mind)
>
> No, I don’t think so. Though maybe we can release an RC as the first tag in the branch and backport features before releasing a final version? I dunno, I guess you will need to talk to OpenStack release folks on how to proceed.

is it a release team matter?
i thought these were a policy inside neutron.
after all networking-midonet is release:independent.

>
> Ihar



More information about the OpenStack-dev mailing list