Date: Wed, 15 May 2019 17:58:38 +0200 From: Kurt Jaeger <pi@freebsd.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515155838.GV20962@fc.opsec.eu> In-Reply-To: <201905151551.x4FFp0UP067236@fire.js.berklix.net> References: <20190515153836.GU20962@fc.opsec.eu> <201905151551.x4FFp0UP067236@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > > 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. > True as far as that goes for binary users, but often source patches > are available faster, which begs the question: when to announce ? > When there's diffs ? When diffs are commited to src/ (used to be the norm *) ? > When there's some binary update ? > Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! Now I understand why you bring this up. I guess the majority of users are using the binary update path. Maybe re@ can explain how the process is for these steps ? -- 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?20190515155838.GV20962>