Date: Wed, 15 May 2019 17:32:09 +0200 From: "Julian H. Stacey" <jhs@berklix.com> To: Kurt Jaeger <pi@freebsd.org> Cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <201905151532.x4FFW9SD066919@fire.js.berklix.net> In-Reply-To: Your message "Wed, 15 May 2019 16:33:21 %2B0200." <20190515143321.GZ72200@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Kurt Jaeger wrote: > 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. Do not do extra work delaying, storing, batch announcing. Announcements to recipients not delayed, without flooding. > > -- > pi@opsec.eu +49 171 3101372 One year to go ! > Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201905151532.x4FFW9SD066919>