Request stable/mitaka 2.0.1 release for networking-ofagent

[fumihiko kakuma]

Please release the new version of stable/mitaka branch for networking-ofagent.

tag: 2.0.1

commit id:

commit baac62f117d0396ac8e044da119a1c6d5f61a57b
Author: fumihiko kakuma <email address hidden>
Date: Mon Mar 28 15:03:10 2016 +0900

    Update a branch environment for stable/mitaka

    Update .gitreview and tools/tox_install.sh

    Change-Id: I8cff76cf3862f2326d729d5d22ad01b83cdb27e7

[fumihiko kakuma (kakuma)]

Currently can I request release of a new version of stable branch for ofagent using openstack/releases repo?

[Doug Wiegley (dougwig)]

Bumping to ihar

[fumihiko kakuma (kakuma)]

Do I need to update release repository[1] by myself?

[1] http://git.openstack.org/cgit/openstack/releases/tree/deliverables/_independent/networking-ofagent.yaml

[fumihiko kakuma (kakuma)]

As 2.0.0 is not recorded on releases repository.

[fumihiko kakuma (kakuma)]

I pushed a bugfix[1] for stable/mitaka now.
So I want to wait this merged patch for 2.0.1 release.

[1] https://review.openstack.org/#/c/308084/

Thank you,
fumihiko kakuma

[Ihar Hrachyshka (ihar-hrachyshka)]

I may miss something, but the only patch on stable/mitaka that is not released yet is:

commit baac62f117d0396ac8e044da119a1c6d5f61a57b
Author: fumihiko kakuma <email address hidden>
Date: Mon Mar 28 15:03:10 2016 +0900

    Update a branch environment for stable/mitaka

    Update .gitreview and tools/tox_install.sh

    Change-Id: I8cff76cf3862f2326d729d5d22ad01b83cdb27e7

Why do you think it justifies a new release?

[fumihiko kakuma (kakuma)]

Sorry, I was not aware of your comment.

There are some patches on stable/mitaka.
I thought that they are merged soon and I was waiting patches to be merged.
But I think to release current merged patches now.
Please release at the following latest commit.

commit bde7b5536bf65d9c19bba0d2eb5ed490b16d1f7d
Author: OpenStack Proposal Bot <email address hidden>
Date: Fri Apr 29 22:37:28 2016 +0000

    Updated from global requirements

    Change-Id: I09697b6ea41539ef943878b9153d9015678a0f8e

[fumihiko kakuma (kakuma)]

The correct commit-id was the following.

commit 817cba30b8896db1b6dcc68791b26a39df4ba11e
Merge: bde7b55 e3d09ce
Author: Jenkins <email address hidden>
Date: Wed Jun 8 12:57:36 2016 +0000

    Merge "Fix coverage option" into stable/mitaka

[Ihar Hrachyshka (ihar-hrachyshka)]

Fumihiko, you should move Incomplete bugs back to Confirmed or New to make it on my radar.

[fumihiko kakuma (kakuma)]

Ah thanks Ihar.
I also added the following patch in release repo.

https://review.openstack.org/#/c/334692/
https://review.openstack.org/#/c/334687/

[Ihar Hrachyshka (ihar-hrachyshka)]

@fumihiko, I still don't see why a release is needed, since all patches are purely infrastructural (tweaking tox targets etc.) I don't think we should release every single patch.

[fumihiko kakuma (kakuma)]

Ihar,

Yes, they are not surely critical patches. But the following is documented for a release to stable branch. http://docs.openstack.org/project-team-guide/stable-branches.html#release-often

[Armando Migliaccio (armando-migliaccio)]

Please be familiar with:

https://review.openstack.org/#/c/308984/

[Armando Migliaccio (armando-migliaccio)]

I would agree with Ihar's recommendation.