[puppet] Retiring puppet-qdr
Hello, Let me restore my old proposal[1] about puppet-qdr. # I lost access to my old emails so I'm starting a new thread. In the previous mail I proposed deprecation instead of retirement, because the module has been used by TripleO. However I noticed that TripleO is now under the process of complete retirement[2]. So, I'd like to revise my proposal, and propose retiring the module completely. Please let me know if you have any concern with this module retired. Unless I hear any objections, I'll start the official retirement process. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034742.h... [2] https://review.opendev.org/c/openstack/governance/+/905145 Thank you, Takashi Kajinami irc: tkajinam
+1 for retiring the module, thanks! Best regards Tobias
On 18 Jan 2024, at 16:58, Takashi Kajinami <kajinamit@oss.nttdata.com> wrote:
Hello,
Let me restore my old proposal[1] about puppet-qdr. # I lost access to my old emails so I'm starting a new thread.
In the previous mail I proposed deprecation instead of retirement, because the module has been used by TripleO. However I noticed that TripleO is now under the process of complete retirement[2]. So, I'd like to revise my proposal, and propose retiring the module completely.
Please let me know if you have any concern with this module retired. Unless I hear any objections, I'll start the official retirement process.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034742.h... [2] https://review.opendev.org/c/openstack/governance/+/905145
Thank you, Takashi Kajinami irc: tkajinam
Because we haven't heard any objections but only a positive response, I'll start the process to retire the repository. On 1/23/24 00:09, Tobias Urdin wrote:
+1 for retiring the module, thanks!
Best regards Tobias
On 18 Jan 2024, at 16:58, Takashi Kajinami <kajinamit@oss.nttdata.com> wrote:
Hello,
Let me restore my old proposal[1] about puppet-qdr. # I lost access to my old emails so I'm starting a new thread.
In the previous mail I proposed deprecation instead of retirement, because the module has been used by TripleO. However I noticed that TripleO is now under the process of complete retirement[2]. So, I'd like to revise my proposal, and propose retiring the module completely.
Please let me know if you have any concern with this module retired. Unless I hear any objections, I'll start the official retirement process.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034742.h... [2] https://review.opendev.org/c/openstack/governance/+/905145
Thank you, Takashi Kajinami irc: tkajinam
participants (2)
-
Takashi Kajinami
-
Tobias Urdin