[openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Takashi Yamamoto yamamoto at midokura.com
Mon Feb 6 01:32:10 UTC 2017


On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto <yamamoto at midokura.com> wrote:
> hi,
>
> On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann <doug at doughellmann.com> wrote:
>> Excerpts from Takashi Yamamoto's message of 2017-01-26 11:42:48 +0900:
>>> hi,
>>>
>>> On Sat, Jan 14, 2017 at 2:17 AM, Doug Hellmann <doug at doughellmann.com> wrote:
>>> > Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600:
>>> >> 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto <yamamoto at midokura.com>:
>>> >> > hi,
>>> >> >
>>> >> > On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <armamig at gmail.com> wrote:
>>> >> >> Hi
>>> >> >>
>>> >> >> As of today, the project neutron-vpnaas is no longer part of the neutron
>>> >> >> governance. This was a decision reached after the project saw a dramatic
>>> >> >> drop in active development over a prolonged period of time.
>>> >> >>
>>> >> >> What does this mean in practice?
>>> >> >>
>>> >> >> From a visibility point of view, release notes and documentation will no
>>> >> >> longer appear on openstack.org as of Ocata going forward.
>>> >> >> No more releases will be published by the neutron release team.
>>> >> >> The neutron team will stop proposing fixes for the upstream CI, if not
>>> >> >> solely on a voluntary basis (e.g. I still felt like proposing [2]).
>>> >> >>
>>> >> >> How does it affect you, the user or the deployer?
>>> >> >>
>>> >> >> You can continue to use vpnaas and its CLI via the python-neutronclient and
>>> >> >> expect it to work with neutron up until the newton
>>> >> >> release/python-neutronclient 6.0.0. After this point, if you want a release
>>> >> >> that works for Ocata or newer, you need to proactively request a release
>>> >> >> [5], and reach out to a member of the neutron release team [3] for approval.
>>> >> >
>>> >> > i want to make an ocata release. (and more importantly the stable branch,
>>> >> > for the benefit of consuming subprojects)
>>> >> > for the purpose, the next step would be ocata-3, right?
>>> >>
>>> >> Hey Takashi,
>>> >> If you want to release new version of neutron-vpnaas, please look at [1].
>>> >> This is the place, which you need to update and based on provided
>>> >> details, tags and branches will be cut.
>>> >>
>>> >> [1] https://github.com/openstack/releases/blob/master/deliverables/ocata/neutron-vpnaas.yaml
>>> >
>>> > Unfortunately, since vpnaas is no longer part of an official project,
>>> > we won't be using the releases repository to manage and publish
>>> > information about the releases. It'll need to be done by hand.
>>>
>>> who can/should do it by hand?
>>
>> I can do it. Let me know the version number, and for each repository the
>> SHA of the commit on the master branch to be tagged.

please make it with the following.  thank you!

stable/ocata
10.0.0
openstack/neutron-vpnaas
d6db1238a4950df03dfb28acabcf4df14ebfa3ac

>
> thank you. i'll ask you when necessary.
>
> i think it's fine to just make a branch from master when stable branch is cut
> for neutron.  how others think?
>
>>
>> Doug
>>
>>>
>>> >
>>> > Doug
>>> >
>>> >>
>>> >> BR, Dariusz
>>> >>
>>> >
>>> > __________________________________________________________________________
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list