Date: Sat, 18 Dec 2010 13:15:38 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: RFC: Upgrade BIND version in RELENG_7 to BIND 9.6.x Message-ID: <20101218111538.GZ33073@deviant.kiev.zoral.com.ua> In-Reply-To: <4D0C49A2.4000203@FreeBSD.org> References: <4D0C49A2.4000203@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--s1V7GiNVmT/EiLBY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 17, 2010 at 09:41:54PM -0800, Doug Barton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > Howdy, >=20 > Traditionally for contributed software generally, and BIND in particular > we have tried to keep the major version of the contributed software > consistent throughout a given RELENG_$N branch of FreeBSD. Hopefully the > reasoning for this is obvious, we want to avoid POLA violations. Actually not. My own POV is that we should follow the vendor release cycle, and not the FreeBSD release cycle, for the contributed software. I do not advocate immediate upgrade of the third-party software that reached its EOL, but I think that we should do this without pushback if maintainer consider the neccessity of upgrade. --s1V7GiNVmT/EiLBY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0Ml9kACgkQC3+MBN1Mb4iGeQCg1w2HBxiS2SgK0Sfsd/8w1fYs 96AAniSAijb2k9TbtbjqXKiPF7QUhwhs =7gcR -----END PGP SIGNATURE----- --s1V7GiNVmT/EiLBY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101218111538.GZ33073>