Deprecate ovm

[DaanHoogland]

          I think we should (instead) deprecate ovm?

Originally posted by @DaanHoogland in #10684 (comment)

Vote: https://lists.apache.org/thread/oxdw4psw43w1fp3yz5knx30fq34pp6x6
The final removal will be in v22 (estimated end of 2025/beginning of 2026).

[DaanHoogland]

ovm (or oracle VM) is now supported by the standard kvm plugin as oracle linux. The older modules do not work.

[JoaoJandre]

Hello, @DaanHoogland

I don't see a reason to keep OVM support, so I agree that it should be deprecated.

I would like to see the discussion regarding versioning going forward, so that we can eventually actually remove OVM support, and not keep it deprecated until the end of times.

I'll try to revive the discussion once again in the mailing list, we have lots of dead code that should be deprecated/removed.

[DaanHoogland]

@JoaoJandre deprecation of plugins has a procedure, @rafaelweingartner created it. I have been looking for it on cwiki and in the mail list but have not found the reference yet.

Of the top off my head:

• a plugin is marked as deprecated
• at least 6 moths later and in a next major release it is removed.

anybody can object, of course but must than show maintenance effort.

happy to adjust the procedure if needed (or if I’m wrong)

[weizhouapache]

+1
I think it should be decided by PMC, and announced to community with clear versions (deprecation and removal)

maybe for each plugin, (1) an official vote by PMC; (2) an email for announcement (3) a github issue for followup; (4) a github PR for removal

[DaanHoogland]

sounds good, (and about what I remember, though one remark, This should be a public vote, on dev@. Any contributor should be able to veto and/if they volunteer as a maintainer.

[DaanHoogland]

justr as a reference, rafael gave me the link to the (old) procedure off-lineish: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68720798

I think it is still mostly valid.

cc @JoaoJandre @weizhouapache

[weizhouapache]

justr as a reference, rafael gave me the link to the (old) procedure off-lineish: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68720798

I think it is still mostly valid.

cc @JoaoJandre @weizhouapache

looks good

[JoaoJandre]

@weizhouapache @DaanHoogland I've seen the procedure, it looks good to me, but I think we should update it so that the component only be removed on major versions. I've sent a message on the dev mailing list regarding it.

In any case, just to make things clear, I'm 100% +1 on removing OVM (and other dead code), I just believe that it shouldn't be done in a minor version.

[DaanHoogland]

@weizhouapache @DaanHoogland I've seen the procedure, it looks good to me, but I think we should update it so that the component only be removed on major versions. I've sent a message on the dev mailing list regarding it.

In any case, just to make things clear, I'm 100% +1 on removing OVM (and other dead code), I just believe that it shouldn't be done in a minor version.

I can concur but I think that the deprecation can happen on a minor version, not the deletion. (I’ll surely encounter the mail soon ;)

[DaanHoogland]

so that we don’ t let the formal discussion stand in the way of the practical cleanup, I marked this for milestone 21, so actual removal would be in 22. (possible issue with the minor/major versions avoided)