sysutils/rundeck{2,3}: drop maintainership

[fuz]

Summary

sysutils/rundeck{2,3}: drop maintainership

PR:		261748
Approved by:	... (mentor)

Test Plan

n/a

[flo]

Approved

[diizzy]

As mentioned in PR deprecate 2.x and set EXPIRATION_DATE appropriately. Please don't just dump old unmaintained versions in ports.

[flo]

In D38635#879603, @diizzy wrote:

As mentioned in PR deprecate 2.x and set EXPIRATION_DATE appropriately. Please don't just dump old unmaintained versions in ports.

Well spotted. 2.X should indeed be deprecated, with an expiry of e.g. 31.03.2023. Looking at https://docs.rundeck.com/docs/history/release-calendar.html we might as well deprecate and set an EXPIRATION_DATE on 3.x as well.

The 3.4.x series will not be provided back port security fixes after the 1 year anniversary of 4.0.0 on March 23rd, 2023.

[fuz]

Is it ok if I add the deprecation to the next batch or do you want me to revise this one?

Please note that rundeck4 is not ported, so removing sysutils/rundeck3 would leave users with no replacement port. I am against deprecating it.

[flo]

In D38635#879630, @fuz wrote:

Is it ok if I add the deprecation to the next batch or do you want me to revise this one?

Yeah, separate commit is fine if it simplifies things for you.

Please note that rundeck4 is not ported, so removing sysutils/rundeck3 would leave users with no replacement port. I am against deprecating it.

I noticed. The deprecation message can also be seen as a heads up for current users. Maybe it can get someone interested in porting 4.x. EXPIRATION_DATE can also be 6 or 12 months in the future, and then revisit it. See e.g. the PHP ports. Just make sure to mark your calendar, otherwise Rene will reap the ports as soon as the expiration date is reached :)

These are merely suggestions, not a hard no from me.