Open Stack

Cathy Zhang <Cathy.H.Zhang at 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:ihrachys at 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 <tony at bakeyournoodle.com> wrote:
>
>> On Wed, Jul 06, 2016 at 12:40:48PM +0000, 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