FreeBSD flood of 8 breakage announcements in 3 mins.

[Glen Barber]

On Wed, May 15, 2019 at 05:58:38PM +0200, Kurt Jaeger wrote:
> 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 ?
> 

This is an so@ thing (CCd).  re@ does not have any involvement in this
process.

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20190515/0f311d7e/attachment.sig>