2017-01-12 21:43 GMT-06:00 Takashi Yamamoto <yamam...@midokura.com>:
> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma...@gmail.com> wrote:
>> 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 ).
>> 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
>> , and reach out to a member of the neutron release team  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?
If you want to release new version of neutron-vpnaas, please look at .
This is the place, which you need to update and based on provided
details, tags and branches will be cut.
OpenStack-Infra mailing list