On Wed, Feb 19, 2020 at 05:07:12PM +0100, Slawek Kaplonski wrote:
Hi,
Ussuri-2 milestone is behind us and we still don’t have anyone who would like to maintain neutron-fwaas project upstream. So I just sent patch [1] to add info to project’s docs that it is deprecated in Neutron stadium.
Question, to TC members mostly - should I do also some other actions to officially deprecate this project? Any changes to governance repo or something like that? Thanks in advance for any help with that.
Shall we follow the same process we used for LBaaS in [1] and [2], or does that need to wait? I think there is a good chance we will not see another release of neutron-fwaas code.
Thanks
Nate
[1] https://review.opendev.org/#/c/705780/ [2] https://review.opendev.org/#/c/658493/
[1] https://review.opendev.org/708675
On 20 Jan 2020, at 21:26, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
We are getting closer and closer to Ussuri-2 milestone which is our deadline to deprecate neutron-fwaas project if there will be no any volunteers to maintain this project. So if You are interested in this project, please raise Your hand here or ping me on IRC about that.
On 6 Jan 2020, at 21:05, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Just as a reminder, we are still looking for maintainers who want to keep neutron-fwaas project alive. As it was written in my previous email, we will mark this project as deprecated. So please reply to this email or contact me directly if You are interested in maintaining this project.
On 19 Nov 2019, at 11:26, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Over the past couple of cycles we have noticed that new contributions and maintenance efforts for neutron-fwaas project were almost non existent. This impacts patches for bug fixes, new features and reviews. The Neutron core team is trying to at least keep the CI of this project healthy, but we don’t have enough knowledge about the details of the neutron-fwaas code base to review more complex patches.
During the PTG in Shanghai we discussed that with operators and TC members during the forum session [1] and later within the Neutron team during the PTG session [2].
During these discussions, with the help of operators and TC members, we reached the conclusion that we need to have someone responsible for maintaining project. This doesn’t mean that the maintainer needs to spend full time working on this project. Rather, we need someone to be the contact person for the project, who takes care of the project’s CI and review patches. Of course that’s only a minimal requirement. If the new maintainer works on new features for the project, it’s even better :)
If we don’t have any new maintainer(s) before milestone Ussuri-2, which is Feb 10 - Feb 14 according to [3], we will need to mark neutron-fwaas as deprecated and in “V” cycle we will propose to move the project from the Neutron stadium, hosted in the “openstack/“ namespace, to the unofficial projects hosted in the “x/“ namespace.
So if You are using this project now, or if You have customers who are using it, please consider the possibility of maintaining it. Otherwise, please be aware that it is highly possible that the project will be deprecated and moved out from the official OpenStack projects.
[1] https://etherpad.openstack.org/p/PVG-Neutron-stadium-projects-the-path-forwa... [2] https://etherpad.openstack.org/p/Shanghai-Neutron-Planning-restored - Lines 379-421 [3] https://releases.openstack.org/ussuri/schedule.html
-- Slawek Kaplonski Senior software engineer Red Hat
— Slawek Kaplonski Senior software engineer Red Hat
— Slawek Kaplonski Senior software engineer Red Hat
— Slawek Kaplonski Senior software engineer Red Hat