From owner-freebsd-security@FreeBSD.ORG Thu Apr 10 11:01:19 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4DAD732 for ; Thu, 10 Apr 2014 11:01:19 +0000 (UTC) Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com [IPv6:2607:f8b0:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6BC11395 for ; Thu, 10 Apr 2014 11:01:19 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id id10so3332505vcb.12 for ; Thu, 10 Apr 2014 04:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Kp75rIcmjEHnxJX073ngQogvMaGI4HeWM0HjWyX3VGA=; b=f+N0Xy7+3WYIPz0uLDhln4d6Z13HyOlDsG6yHVzTxNcNzm9ksd/IHB4WSYS/apqpFs Av4mdk6udO0WIwbUDtdoaz0fUtTXfElwgWO1wCrzUGBOPyTCb2n7efl422gyZHdoP2vO 9j7bfCeEhZmG8w3hhuMIx0zaSQY+JtSND7Yy8Z6IvAV5A0rjcyacW9O47E0f8pGzYk0i 3LauHdzSQzJ7QNgtBsgTRYcZVKOcMCrEtUatfpP6Cvx/UcSXdeVxzdotMM1eRg8U5AIK sS5jrCtGjSNO92eoGCxYBf1WX37Gr53U1RW2/6q9tBNvi7IbAXYUdB1EQ6Rc3cWyb7oz K4ww== MIME-Version: 1.0 X-Received: by 10.58.201.5 with SMTP id jw5mr13422892vec.6.1397127678633; Thu, 10 Apr 2014 04:01:18 -0700 (PDT) Received: by 10.221.39.130 with HTTP; Thu, 10 Apr 2014 04:01:18 -0700 (PDT) Date: Thu, 10 Apr 2014 12:01:18 +0100 Message-ID: Subject: Re: Proposal From: Pawel Biernacki To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-security@freebsd.org, Kimmo Paasiala , Walter Hop X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 11:01:20 -0000 On 10 April 2014 08:09, Dag-Erling Sm=C3=B8rgrav wrote: > Pawel Biernacki writes: >> If you want to make an excuse that a build took a long time - it's >> really a poor one. If the build cluster is too slow then project need >> to acquire a new one. > > The freebsd-update build is not a normal make buildworld or make > release, it's much more complicated than that. > So you're telling me that nothing can be done about it? >> Many of us had very hard time during last 48 hours. I know that when >> you fill responsible for something you want to do as much as you can, >> but you need to sleep, eat, etc.. If the whole process is to >> overwhelming for one person maybe it's time to think about extending >> the SO team or reorganising the process of preparing patched releases? >> If there is a need of hands, manpower or so why not ask the community >> to help? > > Did you read the part where I said this is mostly single-threaded? > Yes, but you also wrote: > The best you can hope for is to have someone relieve > you while you eat and sleep. And I don't understand why all of those things need to be single-threaded, since you even mention asking someone from clusteradm@ to help: > Once the builds were ready to go, he moved into a phase where everything > had to happen more or less simultaneously: commit the patches, finalize > the advisory (which contains revision numbers and timestamps), sign it, > then commit the advisory and the patch to the doc tree, update the > relevant portions of the web site, wait for them to propagate (or grab a > passing member of clusteradm@ and have them push it through manually), > and finally mail out the advisory. --=20 One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die= .