Re: [openstack-dev] [Neutron] SFC stable/mitaka version

[Ihar Hrachyshka]

Akihiro Motoki  wrote:


2016-07-29 18:34 GMT+09:00 Ihar Hrachyshka :

Cathy Zhang  wrote:


Hi Ihar and all,

Yes, we have been preparing for such a release. We will do one more round
of testing to make sure everything works fine, and then I will submit the
release request.
There is a new patch on "stadium: adopt openstack/releases in subproject
release process" which is not Merged yet.
Shall I follow this
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process
to submit the request?
Do you have a good bug example for Neutron sub-project release request?



For the time being, until the patch landds, you may follow any of those
directions.

An example of a release request bug is:
https://bugs.launchpad.net/networking-bagpipe/+bug/1589502


BTW, a functional and tempest patch for networking-sfc has been uploaded
and it might take some time for the team to complete the review. The  
test is

non-voting. Do you think we should wait until this patch is merged or
release can be done without it?



It would be great to have CI voting, but then, you already lag with the
release for months comparing to release date of Neutron Mitaka, and you  
risk

getting into Phase II support mode before you even release the first
version. If you don’t envision release blocker bugs in the branch, I would
suggest you release the thing and then follow up with bug fixes for  
whatever

you catch later on. In a way, it’s better to release a half baked release
than to not release at all. That’s to follow the ‘release often’ mantra,  
and

boost adoption.


I agree with Ihar, but I think there are several points to be checked
before the release.

- The code should be tested against mitaka version of neutron.
  Currently the master branch of networking-sfc is tested against neutron master
  and we haven't tested it against neutron stable/mitaka after Mitaka
was released.


That’s why we suggest* in devref to release at around same time as neutron:

*  
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#stable-branches


"Stable branches for subprojects should be created at the same time when  
corresponding neutron stable branches are created. This is to avoid  
situations when a postponed cut-off results in a stable branch that  
contains some patches that belong to the next release. This would require  
reverting patches, and this is something you should avoid."




- networking-sfc branch already contains newton db migration (see
db/migration/alambic_migrations/versions/newton).
  What I am not sure is whether it needs to be a part of mitaka release or not,
  but you need to be careful when cutting stable/mitaka branch.


Good catch. From alembic perspective, it does not matter where scripts are  
located, so it’s probably minor.


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] SFC stable/mitaka version

[Akihiro Motoki]

2016-07-29 18:34 GMT+09:00 Ihar Hrachyshka <ihrac...@redhat.com>:
> Cathy Zhang <cathy.h.zh...@huawei.com> wrote:
>
>> Hi Ihar and all,
>>
>> Yes, we have been preparing for such a release. We will do one more round
>> of testing to make sure everything works fine, and then I will submit the
>> release request.
>> There is a new patch on "stadium: adopt openstack/releases in subproject
>> release process" which is not Merged yet.
>> Shall I follow this
>> http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process
>> to submit the request?
>> Do you have a good bug example for Neutron sub-project release request?
>
>
> For the time being, until the patch landds, you may follow any of those
> directions.
>
> An example of a release request bug is:
> https://bugs.launchpad.net/networking-bagpipe/+bug/1589502
>
>>
>> BTW, a functional and tempest patch for networking-sfc has been uploaded
>> and it might take some time for the team to complete the review. The test is
>> non-voting. Do you think we should wait until this patch is merged or
>> release can be done without it?
>
>
> It would be great to have CI voting, but then, you already lag with the
> release for months comparing to release date of Neutron Mitaka, and you risk
> getting into Phase II support mode before you even release the first
> version. If you don’t envision release blocker bugs in the branch, I would
> suggest you release the thing and then follow up with bug fixes for whatever
> you catch later on. In a way, it’s better to release a half baked release
> than to not release at all. That’s to follow the ‘release often’ mantra, and
> boost adoption.

I agree with Ihar, but I think there are several points to be checked
before the release.

- The code should be tested against mitaka version of neutron.
  Currently the master branch of networking-sfc is tested against neutron master
  and we haven't tested it against neutron stable/mitaka after Mitaka
was released.

- networking-sfc branch already contains newton db migration (see
db/migration/alambic_migrations/versions/newton).
  What I am not sure is whether it needs to be a part of mitaka release or not,
  but you need to be careful when cutting stable/mitaka branch.

Thanks,
Akihiro


>
>
>>
>> Thanks,
>> Cathy
>>
>> -----Original Message-----
>> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
>> Sent: Wednesday, July 27, 2016 1:24 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version
>>
>> Tony Breeds <t...@bakeyournoodle.com> wrote:
>>
>>> On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:
>>>>
>>>> Hi,
>>>> Is anyone looking at creating a stable/mitaka version? What if
>>>> someone want to use this for stable/mitaka?
>>>
>>>
>>> If that's a thing you need it's a matter of Armando asking the release
>>> managers to create it.
>>
>>
>> I only suggest Armando is not dragged into it, the release liaison
>> (currently me) should be able to handle the request if it comes from the
>> core team for the subproject.
>>
>> 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

__
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] SFC stable/mitaka version

[Ihar Hrachyshka]

Cathy Zhang <cathy.h.zh...@huawei.com> wrote:


Hi Ihar and all,

Yes, we have been preparing for such a release. We will do one more round  
of testing to make sure everything works fine, and then I will submit the  
release request.
There is a new patch on "stadium: adopt openstack/releases in subproject  
release process" which is not Merged yet.
Shall I follow this  
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process  
to submit the request?

Do you have a good bug example for Neutron sub-project release request?


For the time being, until the patch landds, you may follow any of those  
directions.


An example of a release request bug is:  
https://bugs.launchpad.net/networking-bagpipe/+bug/1589502




BTW, a functional and tempest patch for networking-sfc has been uploaded  
and it might take some time for the team to complete the review. The test  
is non-voting. Do you think we should wait until this patch is merged or  
release can be done without it?


It would be great to have CI voting, but then, you already lag with the  
release for months comparing to release date of Neutron Mitaka, and you  
risk getting into Phase II support mode before you even release the first  
version. If you don’t envision release blocker bugs in the branch, I would  
suggest you release the thing and then follow up with bug fixes for  
whatever you catch later on. In a way, it’s better to release a half baked  
release than to not release at all. That’s to follow the ‘release often’  
mantra, and boost adoption.




Thanks,
Cathy

-Original Message-
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
Sent: Wednesday, July 27, 2016 1:24 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version

Tony Breeds <t...@bakeyournoodle.com> wrote:


On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:

Hi,
Is anyone looking at creating a stable/mitaka version? What if
someone want to use this for stable/mitaka?


If that's a thing you need it's a matter of Armando asking the release
managers to create it.


I only suggest Armando is not dragged into it, the release liaison  
(currently me) should be able to handle the request if it comes from the  
core team for the subproject.


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] SFC stable/mitaka version

[Cathy Zhang]

Hi Assaf,

Yes, that makes sense. 

Thanks,
Cathy

-Original Message-
From: Assaf Muller [mailto:as...@redhat.com] 
Sent: Thursday, July 28, 2016 1:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version

On Thu, Jul 28, 2016 at 3:02 PM, Cathy Zhang <cathy.h.zh...@huawei.com> wrote:
> Hi Ihar and all,
>
> Yes, we have been preparing for such a release. We will do one more round of 
> testing to make sure everything works fine, and then I will submit the 
> release request.
> There is a new patch on "stadium: adopt openstack/releases in subproject 
> release process" which is not Merged yet.
> Shall I follow this 
> http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process
>  to submit the request?
> Do you have a good bug example for Neutron sub-project release request?
>
> BTW, a functional and tempest patch for networking-sfc has been uploaded and 
> it might take some time for the team to complete the review. The test is 
> non-voting. Do you think we should wait until this patch is merged or release 
> can be done without it?

The ideal is that any testing you're doing downstream or manually should be 
happening upstream and via CI. If you feel the need to run things one more time 
then that means that the upstream CI that is running for SFC is insufficient. A 
secondary incentive is to boost adoption - People tend to be attracted to 
stable projects with higher quality testing. I would advise accelerating the 
functional and tempest tests patches and releasing when your CI is in a better 
state.

>
> Thanks,
> Cathy
>
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Wednesday, July 27, 2016 1:24 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version
>
> Tony Breeds <t...@bakeyournoodle.com> wrote:
>
>> On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:
>>> Hi,
>>> Is anyone looking at creating a stable/mitaka version? What if 
>>> someone want to use this for stable/mitaka?
>>
>> If that's a thing you need it's a matter of Armando asking the 
>> release managers to create it.
>
> I only suggest Armando is not dragged into it, the release liaison (currently 
> me) should be able to handle the request if it comes from the core team for 
> the subproject.
>
> 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

__
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

__
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] SFC stable/mitaka version

[Assaf Muller]

On Thu, Jul 28, 2016 at 3:02 PM, Cathy Zhang <cathy.h.zh...@huawei.com> wrote:
> Hi Ihar and all,
>
> Yes, we have been preparing for such a release. We will do one more round of 
> testing to make sure everything works fine, and then I will submit the 
> release request.
> There is a new patch on "stadium: adopt openstack/releases in subproject 
> release process" which is not Merged yet.
> Shall I follow this 
> http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process
>  to submit the request?
> Do you have a good bug example for Neutron sub-project release request?
>
> BTW, a functional and tempest patch for networking-sfc has been uploaded and 
> it might take some time for the team to complete the review. The test is 
> non-voting. Do you think we should wait until this patch is merged or release 
> can be done without it?

The ideal is that any testing you're doing downstream or manually
should be happening upstream and via CI. If you feel the need to run
things one more time then that means that the upstream CI that is
running for SFC is insufficient. A secondary incentive is to boost
adoption - People tend to be attracted to stable projects with higher
quality testing. I would advise accelerating the functional and
tempest tests patches and releasing when your CI is in a better state.

>
> Thanks,
> Cathy
>
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Wednesday, July 27, 2016 1:24 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version
>
> Tony Breeds <t...@bakeyournoodle.com> wrote:
>
>> On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:
>>> Hi,
>>> Is anyone looking at creating a stable/mitaka version? What if
>>> someone want to use this for stable/mitaka?
>>
>> If that's a thing you need it's a matter of Armando asking the release
>> managers to create it.
>
> I only suggest Armando is not dragged into it, the release liaison (currently 
> me) should be able to handle the request if it comes from the core team for 
> the subproject.
>
> 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

__
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] SFC stable/mitaka version

[Cathy Zhang]

Hi Ihar and all,

Yes, we have been preparing for such a release. We will do one more round of 
testing to make sure everything works fine, and then I will submit the release 
request. 
There is a new patch on "stadium: adopt openstack/releases in subproject 
release process" which is not Merged yet. 
Shall I follow this 
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html#sub-project-release-process
 to submit the request? 
Do you have a good bug example for Neutron sub-project release request?  

BTW, a functional and tempest patch for networking-sfc has been uploaded and it 
might take some time for the team to complete the review. The test is 
non-voting. Do you think we should wait until this patch is merged or release 
can be done without it? 

Thanks,
Cathy

-Original Message-
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] 
Sent: Wednesday, July 27, 2016 1:24 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version

Tony Breeds <t...@bakeyournoodle.com> wrote:

> On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:
>> Hi,
>> Is anyone looking at creating a stable/mitaka version? What if 
>> someone want to use this for stable/mitaka?
>
> If that's a thing you need it's a matter of Armando asking the release 
> managers to create it.

I only suggest Armando is not dragged into it, the release liaison (currently 
me) should be able to handle the request if it comes from the core team for the 
subproject.

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] SFC stable/mitaka version

[Tony Breeds]

On Wed, Jul 27, 2016 at 10:23:30PM +0200, Ihar Hrachyshka wrote:

> I only suggest Armando is not dragged into it, the release liaison
> (currently me) should be able to handle the request if it comes from the
> core team for the subproject.

Good point.  I defaulted to PTL but you're right the release liason is also
totally reasonable.

Yours Tony.


signature.asc
Description: PGP signature
__
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] SFC stable/mitaka version

[Ihar Hrachyshka]

Tony Breeds  wrote:


On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:

Hi,
Is anyone looking at creating a stable/mitaka version? What if someone  
want

to use this for stable/mitaka?


If that's a thing you need it's a matter of Armando asking the release  
managers

to create it.


I only suggest Armando is not dragged into it, the release liaison  
(currently me) should be able to handle the request if it comes from the  
core team for the subproject.


Ihar


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] SFC stable/mitaka version

[Tony Breeds]

On Wed, Jul 06, 2016 at 12:40:48PM +, Gary Kotton wrote:
> Hi,
> Is anyone looking at creating a stable/mitaka version? What if someone want
> to use this for stable/mitaka?

If that's a thing you need it's a matter of Armando asking the release managers
to create it.

Yours Tony.


signature.asc
Description: PGP signature
__
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

[openstack-dev] [Neutron] SFC stable/mitaka version

[Gary Kotton]

Hi,
Is anyone looking at creating a stable/mitaka version? What if someone want to 
use this for stable/mitaka?
Thanks
Gary
__
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