From owner-freebsd-security@FreeBSD.ORG  Thu Apr 10 07:09:12 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3182CD24
 for <freebsd-security@freebsd.org>; Thu, 10 Apr 2014 07:09:12 +0000 (UTC)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id E682B1B7C
 for <freebsd-security@freebsd.org>; Thu, 10 Apr 2014 07:09:11 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id E3E066B05;
 Thu, 10 Apr 2014 07:09:09 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id 76406930; Thu, 10 Apr 2014 09:09:10 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Pawel Biernacki <pawel.biernacki@gmail.com>
Subject: Re: Proposal
References: <9eeba1ab-2ab0-4188-82aa-686c5573a5db@me.com>
 <8D81F198-36A7-47F4-B486-DA059910A6B4@spam.lifeforms.nl>
 <867g6y1kfe.fsf@nine.des.no>
 <CAA3htvv_DePi_A-UjtG0hvybfRSE8KgvSjq5m3yM0FGX9+L6QQ@mail.gmail.com>
Date: Thu, 10 Apr 2014 09:09:09 +0200
In-Reply-To: <CAA3htvv_DePi_A-UjtG0hvybfRSE8KgvSjq5m3yM0FGX9+L6QQ@mail.gmail.com>
 (Pawel Biernacki's message of "Wed, 9 Apr 2014 23:46:35 +0100")
Message-ID: <86ioqh7jai.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@freebsd.org, Kimmo Paasiala <kpaasial@icloud.com>,
 Walter Hop <freebsd@spam.lifeforms.nl>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 07:09:12 -0000

Pawel Biernacki <pawel.biernacki@gmail.com> 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.

> 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?

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no