Re: [openstack-dev] [neutron][stable] Understanding stable/branch process for Neutron subprojects

On 06/11/15 13:46, Ihar Hrachyshka wrote: > Neil Jerram wrote: > >> Prompted by the thread about maybe allowing subproject teams to do their >> own stable maint, I have some questions about what I should be doing in >> networking-calico; and I guess the answers may

Re: [openstack-dev] [neutron][stable] Understanding stable/branch process for Neutron subprojects

>>> >> All new features must go to master only. Your master should always be >> tested and work with neutron master (meaning, your master should target >> Mitaka, not Liberty). >> >>> We have a very similar situation in networking-infoblox to what Neil was saying about Calico. In our

[openstack-dev] [neutron][stable] Understanding stable/branch process for Neutron subprojects

Prompted by the thread about maybe allowing subproject teams to do their own stable maint, I have some questions about what I should be doing in networking-calico; and I guess the answers may apply generally to subprojects. Let's start from the text at

Re: [openstack-dev] [neutron][stable] Understanding stable/branch process for Neutron subprojects

Neil Jerram wrote: Prompted by the thread about maybe allowing subproject teams to do their own stable maint, I have some questions about what I should be doing in networking-calico; and I guess the answers may apply generally to subprojects. Let's start from the