Date: Wed, 15 May 2019 17:38:36 +0200 From: Kurt Jaeger <pi@freebsd.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515153836.GU20962@fc.opsec.eu> In-Reply-To: <201905151532.x4FFW9SD066919@fire.js.berklix.net> References: <20190515143321.GZ72200@home.opsec.eu> <201905151532.x4FFW9SD066919@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > But those styled as 'management' who delay announcements to batch floods > > > damage us. > > > > 8 announcements and one freebsd-update is easier on the > > admin and the re-team than 8 announcements and 8 freebsd-update runs. > > > > That's probably why they are batched. Because all of the fixes > > are bundled in one update. > > > > If the re-team-capacity is limited, what would be the alternative? > Alternative is to for announcers to do Less work: > Send each announcement when ready. The problem is not the announcement, the problem is providing the freebsd-update. If announcements are send when ready, and the freebsd-update is not ready, therefore, the timeframes to attack systems with unpatched problems are much longer. -- pi@FreeBSD.org +49 171 3101372 One year to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190515153836.GU20962>