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

2016-11-25 Thread Takashi Yamamoto
On Fri, Nov 25, 2016 at 8:02 PM, Ihar Hrachyshka  wrote:
>
>> On 25 Nov 2016, at 11:02, Takashi Yamamoto  wrote:
>>
>> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka  wrote:
>>>
 On 25 Nov 2016, at 09:25, Takashi Yamamoto  wrote:

 On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka  
 wrote:
>
>> On 25 Nov 2016, at 05:26, Takashi Yamamoto  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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2016-11-25 Thread Ihar Hrachyshka

> On 25 Nov 2016, at 11:02, Takashi Yamamoto  wrote:
> 
> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka  wrote:
>> 
>>> On 25 Nov 2016, at 09:25, Takashi Yamamoto  wrote:
>>> 
>>> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka  
>>> wrote:
 
> On 25 Nov 2016, at 05:26, Takashi Yamamoto  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.

Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2016-11-25 Thread Takashi Yamamoto
On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka  wrote:
>
>> On 25 Nov 2016, at 09:25, Takashi Yamamoto  wrote:
>>
>> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka  wrote:
>>>
 On 25 Nov 2016, at 05:26, Takashi Yamamoto  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)

>
> I see that subprojects do the same mistake over and over (the previous time 
> it was sfc, but I’ve heard similar concerns from bgpvpn). I believe that we 
> should set clear expectations for all stadium participants about when they 
> first stable releases happen and when branches are created. The current lack 
> of guidelines for participants just makes it harder for the core team to 
> maintain the setting, and for subprojects to become good citizens.
>
> Ihar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2016-11-25 Thread Ihar Hrachyshka

> On 25 Nov 2016, at 09:25, Takashi Yamamoto  wrote:
> 
> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka  wrote:
>> 
>>> On 25 Nov 2016, at 05:26, Takashi Yamamoto  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.

> 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.)

I see that subprojects do the same mistake over and over (the previous time it 
was sfc, but I’ve heard similar concerns from bgpvpn). I believe that we should 
set clear expectations for all stadium participants about when they first 
stable releases happen and when branches are created. The current lack of 
guidelines for participants just makes it harder for the core team to maintain 
the setting, and for subprojects to become good citizens.

Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2016-11-25 Thread Takashi Yamamoto
On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka  wrote:
>
>> On 25 Nov 2016, at 05:26, Takashi Yamamoto  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?

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.

>
>>
>> On Fri, Nov 25, 2016 at 9:14 AM, Ihar Hrachyshka  wrote:
>>> Hi,
>>>
>>> could anyone from the midonet subproject take ownership of repo stable
>>> branches? Newton branch is broken for weeks with no apparent actions from
>>> the core team side.
>>>
>>> Begin forwarded message:
>>>
>>> From: "A mailing list for the OpenStack Stable Branch test reports."
>>> 
>>> Subject: [Openstack-stable-maint] Stable check of
>>> openstack/networking-midonet failed
>>> Date: 24 November 2016 at 07:11:42 GMT+1
>>> To: openstack-stable-ma...@lists.openstack.org
>>> Reply-To: openstack-dev@lists.openstack.org
>>>
>>> Build failed.
>>>
>>> - periodic-networking-midonet-docs-liberty
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-liberty/b912665/
>>> : SUCCESS in 4m 58s
>>> - periodic-networking-midonet-python27-liberty
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-liberty/978a77c/
>>> : SUCCESS in 9m 57s
>>> - periodic-networking-midonet-docs-mitaka
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-mitaka/e4e139e/
>>> : SUCCESS in 2m 19s
>>> - periodic-networking-midonet-python27-mitaka
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-mitaka/d61abf6/
>>> : SUCCESS in 7m 06s
>>> - periodic-networking-midonet-docs-newton
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-newton/55ae3d1/
>>> : SUCCESS in 2m 34s
>>> - periodic-networking-midonet-python27-newton
>>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-newton/db864e6/
>>> : FAILURE in 3m 57s
>>>
>>> ___
>>> Openstack-stable-maint mailing list
>>> openstack-stable-ma...@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
>>>
>>>
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

2016-11-25 Thread Ihar Hrachyshka

> On 25 Nov 2016, at 05:26, Takashi Yamamoto  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.

> 
> On Fri, Nov 25, 2016 at 9:14 AM, Ihar Hrachyshka  wrote:
>> Hi,
>> 
>> could anyone from the midonet subproject take ownership of repo stable
>> branches? Newton branch is broken for weeks with no apparent actions from
>> the core team side.
>> 
>> Begin forwarded message:
>> 
>> From: "A mailing list for the OpenStack Stable Branch test reports."
>> 
>> Subject: [Openstack-stable-maint] Stable check of
>> openstack/networking-midonet failed
>> Date: 24 November 2016 at 07:11:42 GMT+1
>> To: openstack-stable-ma...@lists.openstack.org
>> Reply-To: openstack-dev@lists.openstack.org
>> 
>> Build failed.
>> 
>> - periodic-networking-midonet-docs-liberty
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-liberty/b912665/
>> : SUCCESS in 4m 58s
>> - periodic-networking-midonet-python27-liberty
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-liberty/978a77c/
>> : SUCCESS in 9m 57s
>> - periodic-networking-midonet-docs-mitaka
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-mitaka/e4e139e/
>> : SUCCESS in 2m 19s
>> - periodic-networking-midonet-python27-mitaka
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-mitaka/d61abf6/
>> : SUCCESS in 7m 06s
>> - periodic-networking-midonet-docs-newton
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-docs-newton/55ae3d1/
>> : SUCCESS in 2m 34s
>> - periodic-networking-midonet-python27-newton
>> http://logs.openstack.org/periodic-stable/periodic-networking-midonet-python27-newton/db864e6/
>> : FAILURE in 3m 57s
>> 
>> ___
>> Openstack-stable-maint mailing list
>> openstack-stable-ma...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
>> 
>> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev