Subject: Re: What is a snapshot?
To: Erik E. Fair <email@example.com>
From: Ask Dr. Stupid <firstname.lastname@example.org>
Date: 08/12/1997 19:39:29
"Erik E. Fair" (Time Keeper) sez:
* The idea behind doing builds frequently is partly to test things as
* immediately as possible after source commit (my own efforts in this area, I
* am told, are appreciated), and to get in the habit of doing this often
* enough so that it's easier to say, "OK, that snapshot from a week ago seems
* to be stable, let's call it the new ``blessed'' snapshot."
You betcher suite-bippee your efforts are appreciated! Your 7/31 snapshot
saved my machine's proverbial butt from software disintegration!
[well, maybe that's a bit dramatic, but you get the idea.]
[That particular snapshot, BTW, is certainly stable -- my system doesn't
get TCP panics anymore. Maybe I haven't exercised it enough. I don't know.]
* Please note, I am not trying to put more work on the portmasters. I'd
* vastly prefer that someone *else* do builds & testing for each port, for
* lots of reasons (don't overwork or overcommit the portmaster, independent
* verification, etc).
* more comments?
I think you are spot on, here. I'd like to see snapshots of this nature
The faster the building machine, the more frequent the snapshot
(I say "building machine here" since I'm under the impression that the
sots with the VAXen aren't about to run "make build" for a week. Doesn't
the kernel alone take a half-day on that beast? An 11/750 took at least
four hours to rebuild the kernel from scratch, and two hours before that
to make the dependencies, if I recall my first work assignment correctly.),
so it would be nice to see SPARC/x86/xc-vax builds once a day, Sun-3
and *68k once every three or so.
* Erik <email@example.com>
"When are people going to wake up and perceive people as people, instead
of giving us convenient little labels, trying to force us to conform to
convenient little molds and perceiving us as convenient little threats?"