Hi Julian H. Stacey! On Fri, 10 Sep 2010 11:20:10 +0200; Julian H. Stacey wrote about 'Re: Policy for removing working code':
>>> If someone is following a RELENG_X (a.k.a -STABLE) or a RELENG_X_Y (a >>> errata fix branch), then they should be reading the stable@ list. >> >> True for RELENG_X, but not for RELENG_X_Y. They shouldn't, because all >> information for security/errata fix branch go to announce@, they don't >> need to read all noise in stable@ just for this. And, what is more important, >> they in fact don't do. So announce@ is the only choice from purely practical >> means. > One option could be a new list perhaps called eg one of > features@ > advisories@ > notifications@ > feature-notifications@ > to carry heads up notification of future feature changes / removals. > Its would be more traffic than > announce@ > but much lower traffic than > stable@ > FreeBSD already has the precedent of > security-notifications@ Umm, no: security-notifications@ is not an addon to, but rather a subset of announce@ for those who don't care about anything except the most important events - security. So announce@ would be sufficient - and Handbook already states that things like call for volunteers go to announce@ (and many feature removal notifications may be not certain if there will be volunteers then). But perhaps your idea is applicable to www.freebsd.org, though. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
