Date: Tue, 6 Sep 2011 23:30:04 -0700 From: Stanislav Sedov <stas@FreeBSD.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: ports@freebsd.org, Mark Linimon <linimon@lonesome.com>, portmgr@FreeBSD.org Subject: Re: sysutils/cfs Message-ID: <20110906233004.f0a93ac6.stas@FreeBSD.org> In-Reply-To: <201109051005.p85A5ZvN005263@fire.js.berklix.net> References: <20110904231821.GC22986@lonesome.com> <201109051005.p85A5ZvN005263@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Tue__6_Sep_2011_23_30_04_-0700_0jLcCITALPJiq/8V Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 05 Sep 2011 12:05:35 +0200 "Julian H. Stacey" <jhs@berklix.com> mentioned: > Mark Linimon wrote: > > On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote: > > > It is not responsible to threaten to remove ports without warning > > > between releases for non urgent reasons. > >=20 > > portmgr has no such policy. > >=20 > > Ports get deleted all the time due to various issues. I prefer to see > > a 1- or 2-month warning via EXPIRATION_DATE, but that's my personal > > preference, not a written policy. > >=20 > > mcl >=20 > Drive by ports shootings are becoming too frequent, & will get > FreeBSD a bad name as immature & poorly managed > A solution: Ensure a policy of expiry dates expire a release after > a warning is given in a previous releases (except in emergency). >=20 I second this opinion. We might have not needed the policy a while ago when such deprecations were rare. Given that we gained several people working actively on this I'd like to see some policy regarding deprecation as well. I saw several occasions when ports were deprecated for no apparent reason, so I can understand Julian and other people dissatisfaction with this. What about requiring that the ports deprecated should be either broken or have known published vulnerabilties for a long period of time (say 6 months) for the start? Personally, I'd also love to see people deprecating ports provide a clear reasoning for deprecation in the commit message (not just "deprecated some old ports" etc), so one won't need to guess if he would like to fix/resurrect the port in the feature? Thanks! --=20 Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail=20 /\ www.asciiribbon.org - against proprietary attachments --Signature=_Tue__6_Sep_2011_23_30_04_-0700_0jLcCITALPJiq/8V Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJOZw9yAAoJEL8lojEJL9nwYW0P/jlOKGPE7xnTy9z8+du4pDHf QaXQjnwLSeK5IE5np5AbeGDRTX++EiUI/nqSdtUgcWXQBh9VjL3SW7d/8NYGnfBh pRqGBVypIp1VEAq1ttVZnvPk6xl/N7w9fIcFxc0FK6hZ0/8PQ9w/kB+HkbGa1GQn 7jyH/vR6odgy7IbU7/bL4ByUS564BRHVggc8KJ9N1zuq3U+3yalAkaE/cd5Vz/93 jg8eo9jmk9rKHjP74jgSxFF5ot982Y9UoSW67yHQPWiB2617562SUoJru28LPNW0 j0qahwRn6PGNm3IGAXA+tinw1KViAFf1vV47LM0OyAxuXcL7FUK5ErOxcl+8EXs/ EcLEABjgUfXCJCF8DTiWTq3BTtlatQ1Jb1v/gyx4R1bVwUQN6E/YSb8sZPqrEAa4 6dt40JpYoA8QpPslhb4NJAtK94dxzeECJCQpJGivWJ5OgydL0hDMdxxNfR2vcUDS 7EoB9Fwvk2SSvhbkHdTNFRdr4p2di3EiXTEOpOZfeg496UlcMT512b6aQhShN7Be UxkcSEtnEC2K6qobfuUVTMrx72v1qPbNfTwlJEAd5COqfZ7VFLGqsJvQrzpnpB9p BgvDaqco+jBWD8ilMI62Lceyc+l4xxQIRldCwA9SGBzF73icA44hhWseAeALI26c t60ktGH2HNIOdXhyQTzP =5CWR -----END PGP SIGNATURE----- --Signature=_Tue__6_Sep_2011_23_30_04_-0700_0jLcCITALPJiq/8V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110906233004.f0a93ac6.stas>