Created attachment 218002 [details]
After dns/knot2-lib is deleted the port dns/knot2 can also be removed.
Is there any possibility that some knot2 config can not run under knot3 ?
Should knot2 be kept at least for a while (mabye with DEPRECATED and EXPIRE) ?
From my own experience I saw an obsolete option just generate a non-blocking warning at validation at startup.
The page https://www.knot-dns.cz/docs/3.0/html/migration.html#upgrade-2-9-x-to-3-0-x states: "Knot DNS version 3.0.x is functionally compatible with 2.9.x.".
So I don't think "cooling down" with DEPRECATED or EXPIRE is needed, but I wouldn't mind having that for a while. But the software will be unmaintained.
What would be nice however, would be something like in Perl5, when you update say perl5-5.26 you automatically get perl5-5.32, but I don't know how and where that's managed.
There is a new 2.X version upstream:
What about update it and mark as deprecated and set an expiry date for two or three months?
Because it seems they will still be maintaining it for a while.
"Since then, it doesn't receive new features or enhancements anymore, but it receives all important fixes. It lacks the latest features, but it's more time-proven."
Like this ?
DEPRECATED= Use knot3, it is functionally compatible with 2.9.x
(In reply to Danilo G. Baio from comment #3)
> Because it seems they will still be maintaining it for a while.
I have to admit that I didn't comprehend that from the announcements, but understood the moment 2.9.7 was released.
I guess I best upgrade the dns/knot2 port AND use these two lines Kurt suggested.