Proposal

[Pawel Biernacki]

On 10 April 2014 08:09, Dag-Erling Smørgrav <des at des.no> wrote:
> Pawel Biernacki <pawel.biernacki at 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.
>

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.

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