Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-06-02 Thread Thierry Carrez 

Mark Voelker wrote:

On Jun 1, 2016, at 12:27 PM, Armando M.  wrote:
[...]
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


Thanks for the quick check! So this is clear from a Defcore perspective. 
Let's continue discussing on the review, and sorry for the noise :)


--
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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-06-01 Thread Mark Voelker 

> On Jun 1, 2016, at 12:27 PM, Armando M.  wrote:
> 
> 
> 
> On 1 June 2016 at 02:28, Thierry Carrez  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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-06-01 Thread Armando M. 
On 1 June 2016 at 02:28, Thierry Carrez  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.


> 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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-06-01 Thread Thierry Carrez 

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.


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.


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.


--
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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Doug Wiegley 
Agreed.

doug

> On May 31, 2016, at 12:12 PM, Armando M.  wrote:
> 
> Hi folks,
> 
> 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'll follow up with a governance change, as I know of the imminent deadline 
> [3].
> 
> Thoughts?
> Armando
> 
> [1] 
> https://governance.openstack.org/reference/tags/release_cycle-with-milestones.html
>  
> 
> [2] 
> https://governance.openstack.org/reference/tags/release_cycle-with-intermediary.html
>  
> 
> [3] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095490.html 
> __
> 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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Ryan Moats 



"Armando M." <arma...@gmail.com> wrote on 05/31/2016 01:12:32 PM:

> From: "Armando M." <arma...@gmail.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Date: 05/31/2016 01:13 PM
> Subject: [openstack-dev] [Neutron][Release] Changing release model
> for *-aas services
>
> Hi folks,
>
> 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'll follow up with a governance change, as I know of the imminent
> deadline [3].
>
> Thoughts?
> Armando
>
> [1] https://governance.openstack.org/reference/tags/release_cycle-
> with-milestones.html
> [2] https://governance.openstack.org/reference/tags/release_cycle-
> with-intermediary.html
>
[3] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095490.html

+1 to this as it makes a *LOT* of sense to me...

Ryan (regXboi)
__
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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Kyle Mestery 
On Tue, May 31, 2016 at 1:12 PM, Armando M.  wrote:
> Hi folks,
>
> 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'll follow up with a governance change, as I know of the imminent deadline
> [3].
>
> Thoughts?
> Armando
>
+1, I've voted as such on the reivew as well [4].

[4] https://review.openstack.org/#/c/323522/

> [1]
> https://governance.openstack.org/reference/tags/release_cycle-with-milestones.html
> [2]
> https://governance.openstack.org/reference/tags/release_cycle-with-intermediary.html
> [3] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095490.html
>
> __
> 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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Armando M. 
On 31 May 2016 at 11:17, Ihar Hrachyshka  wrote:

>
> > On 31 May 2016, at 20:12, Armando M.  wrote:
> >
> > Hi folks,
> >
> > 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.
>
> VPNaaS and FWaaS are the land of the dead these days. Even LBaaS is not
> that active.
>
> +1 for the change.
>

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


>
> Ihar
> __
> 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

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Ihar Hrachyshka 

> On 31 May 2016, at 20:12, Armando M.  wrote:
> 
> Hi folks,
> 
> 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.

VPNaaS and FWaaS are the land of the dead these days. Even LBaaS is not that 
active.

+1 for the change.

Ihar
__
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-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Armando M. 
Hi folks,

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'll follow up with a governance change, as I know of the imminent deadline
[3].

Thoughts?
Armando

[1]
https://governance.openstack.org/reference/tags/release_cycle-with-milestones.html
[2]
https://governance.openstack.org/reference/tags/release_cycle-with-intermediary.html
[3] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095490.html
__
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