> On Jun 1, 2016, at 12:27 PM, Armando M. <arma...@gmail.com> wrote:
>
>
>
> On 1 June 2016 at 02:28, Thierry Carrez <thie...@openstack.org> wrote:
> Armando M. wrote:
> Having looked at the recent commit volume that has been going into the
> *-aas repos, I am considering changing the release model for
> neutron-vpnaas, neutron-fwaas, neutron-lbaas
> from release:cycle-with-milestones [1] to
> release:cycle-with-intermediary [2]. This change will allow us to avoid
> publishing a release at fixed times when there's nothing worth releasing.
>
> I commented on the review, but I think it's easier to discuss this here...
>
> Beyond changing the release model, what you're proposing here is to remove
> functionality from an existing deliverable ("neutron" which was a combination
> of openstack/neutron and openstack/neutron-*aas, released together) and
> making the *aas things separate deliverables.
>
> All I wanted to do is change the release model of the *-aas projects, without
> side effects. I appreciate that the governance structure doesn't seem to
> allow this easily, and I am looking for guidance.
>
>
> From a Defcore perspective, the trademark programs include the "neutron"
> deliverable. So the net effect for DefCore is that you remove functionality
> -- and removing functionality from a Defcore-used project needs extra care
> and heads-up time.
>
> To the best of my knowledge none of the *-aas projects are part of defcore,
> and since [1] has no presence of vpn, fw, lb, nor planned, I thought I was on
> the safe side.
>
Thanks for checking. You are correct: LBaaS, VPNaaS, and FWaaS capabilities
are not present in existing Board-approved DefCore Guidelines, nor have they
been proposed for the next one. [2]
[2] http://git.openstack.org/cgit/openstack/defcore/tree/next.json
At Your Service,
Mark T. Voelker
DefCore Committee Co-Chair
>
> It's probably fine to remove *-aas from the neutron deliverable if there is
> no Defcore capability or designated section there (current or planned).
> Otherwise we need to have a longer conversation that is likely to extend
> beyond the release model deadline tomorrow.
>
> I could not see one in [1]
>
> [1] https://github.com/openstack/defcore/blob/master/2016.01.json
>
>
>
> --
> Thierry Carrez (ttx)
>
>
> __________________________________________________________________________
> 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
