From: IN%"paul@vix.com" "Paul A Vixie" 9-JAN-1995 23:08:53.23 To: IN%"bind-workers@vix.com" CC: Subj: art imitates life Return-path: Received: from "port 4893"@gw.home.vix.com by spcvxa.spc.edu (PMDF V4.3-13 #10) id <01HLNRKXF4U88WXPFN@spcvxa.spc.edu>; Mon, 09 Jan 1995 23:08:44 -0500 (EST) Received: by gw.home.vix.com id AA20482; Mon, 9 Jan 95 18:16:27 -0800 Received: by gw.home.vix.com id AA20478; Mon, 9 Jan 95 18:16:26 -0800 Date: Mon, 09 Jan 1995 18:16:25 -0800 From: Paul A Vixie Subject: art imitates life To: bind-workers@vix.com Message-id: <9501100216.AA20478@gw.home.vix.com> Content-transfer-encoding: 7BIT X-Btw: vix.com is also gw.home.vix.com and vixie.sf.ca.us i know this isn't really bind related, but since a month has gone by after beta14 and i have received enough bug reports to warrant a beta15, the following really hits home for me. ------- Forwarded Message How should a revision level be interpreted? Here's a quick guide for anyone short of a clue: 0.1 WE GOT A REALLY GREAT NEW WAY TO DO THINGS !!! <0.9 Not ready for prime time. 0.9 We think it works, but we won't bet our lives on it. 1.0 Management is on our case; seems like a low risk. 1.01 Okay, we knew about that. All known bugs are fixed. 1.02 Fixes bugs you won't see in 27,000 years, i.e. more than three times the age of the universe. 1.03 Fixes bugs in the bug fixes. 1.04 All right, this REALLY fixes all known bugs. 1.05 Fixes bugs introduced in rev 1.04. 1.1 A new crew hired to write documentation. 1.11 From now on, no comma after "i.e." or "e.g.". 1.2 Somebody actually changed a functional feature. 2.0 New crew hired to write software. Old crew blamed for bugs. 2.01 New crew sending out resumes to placement agencies. 3.0 Re-write the software in another language, go back ten squares. ... return to line 0.1 ------- End of Forwarded Message