On 8 August 2017 at 14:21, Takashi Yamamoto <yamam...@midokura.com> wrote:
> On Wed, Aug 9, 2017 at 12:35 AM, Armando M. <arma...@gmail.com> wrote: > > > > > > On 8 August 2017 at 02:34, Akihiro Motoki <amot...@gmail.com> wrote: > >> > >> I proposed a project-config patch to allow us to release neutron-vpnaas. > >> https://review.openstack.org/#/c/491670/ > >> There is a missing configuration when neutron-vpnaas was pushed out > >> from the neutron stadium. > >> Once the patch is merged and -release group are setup, we can release > >> neutron-vpnaas by ourselves. > > > > > > Is this strictly necessary? I don't see these in other gerrit ACLs > > (irrespective of whether they are part of neutron or not). My > understanding > > is that the release can be fully managed by the openstack release team > once > > a patch like [1] is posted to the openstack/releases project. > > > > [1] https://review.openstack.org/#/c/491429/ > > my understanding is it's necessary for hosted projects > because they are not managed by openstack/releases. > unlike neutron-vpnaas, networking-hyperv is an official project. [2] > > [2] https://github.com/openstack/governance/commit/ > c84d0a702f536a43324212f803e0a43a640c9b56 > > Yes, I ended up picking up a bad example, fault of my stale knowledge of the governance repo. > > > > > >> > >> > >> Akihiro > >> > >> 2017-08-08 10:46 GMT+09:00 Takashi Yamamoto <yamam...@midokura.com>: > >> > hi, > >> > > >> > can anyone with an appropriate permission create a stable/pike > >> > and pike rc1 for neutron-vpnaas? > >> > > >> > stable/pike > >> > 11.0.0.0rc1 > >> > openstack/neutron-vpnaas > >> > 8278615c1f35f98447a3f9692a78ab45e90ee8c6 > >> > > >> > thank you. > >> > > >> > > >> > ____________________________________________________________ > ______________ > >> > 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 > > > > __________________________________________________________________________ > 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
