From owner-freebsd-stable@freebsd.org  Wed May 15 15:58:42 2019
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 246241596ED2
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 15 May 2019 15:58:42 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id B90FC92EEF
 for <freebsd-stable@freebsd.org>; Wed, 15 May 2019 15:58:41 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 76BD61596ECF; Wed, 15 May 2019 15:58:41 +0000 (UTC)
Delivered-To: stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 655E11596ECD
 for <stable@mailman.ysv.freebsd.org>; Wed, 15 May 2019 15:58:41 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1CC8A92EEC;
 Wed, 15 May 2019 15:58:41 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.92 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1hQwIg-000HD3-9N; Wed, 15 May 2019 17:58:38 +0200
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>
References: <20190515153836.GU20962@fc.opsec.eu>
 <201905151551.x4FFp0UP067236@fire.js.berklix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201905151551.x4FFp0UP067236@fire.js.berklix.net>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 15:58:42 -0000

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 !