Date: Wed, 02 Dec 2020 12:13:18 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 249367] dns/knot2: delete port Message-ID: <bug-249367-7788-xoO8ItNq5w@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-249367-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-249367-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249367 Evilham <contact@evilham.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |contact@evilham.com --- Comment #6 from Evilham <contact@evilham.com> --- Hey! Running knot2 on FreeBSD for an associative ISP here. AIUI from knot-dns.cz: > This branch is what used to be Current Stable Branch until it had been re= placed by a new Current Stable Branch. Since then, it doesn't receive new f= eatures or enhancements anymore, but it receives all important fixes. It la= cks the latest features, but it's more time-proven. Basically: the Previous Stable Branch (2.9.X) is roughly equivalent to Free= BSD STABLE and the Current Stable Branch (3.0.X) is roughly equivalent to FreeB= SD RELEASE. Configuration is supposed to be mostly compatible, except for a change of default in synthrecords and some behaviour change in ACL which likely doesn= 't affect many users: https://www.knot-dns.cz/docs/3.0/singlehtml/#upgrade-2-9-x-to-3-0-x Basically: 2.X is supported and, while migration should be easy, there is little reward in forcing such a migration because 3.X has been released. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249367-7788-xoO8ItNq5w>