|
From: Lachlan A. <lh...@us...> - 2003-10-07 12:02:55
|
On Mon, 6 Oct 2003 05:08, Neal Richter wrote: > Mutiny? Ok, Pirate Lachlan. *grin* I don't mean to step on the toes of those who have worked very=20 hard for many years. Apologies to them if I was curt. > I think the issue is that we don't > have a plan to get it to the next step... Good point. > I suggest that on next Sunday Oct 12 we > institute a 'code-freeze' and spend the remainder of Oct testing > the code and call it 3.2RC1. 3.2RC1 goes out Sun Nov 2. Good idea. Do you think the db.words.db bug will be sorted out by=20 then? Does anyone have access to Cygwin? > Proposed plan: > > Testing would consist of us figuring out some way to divide up > test points. The basic idea is to go through the process of > changing the configuration file in reasonable ways and > indexing/searching to formally exercise those verbs. Ideally > we'd like to test each of the approx 200 verbs. A similar method > for each executables command-line switches in needed. Thanks for taking the lead on this, Neal. The testing sounds like a=20 big job! I'll start by tentatively taking attributes starting with A-D, and=20 then post a list of those which I *don't* think I'll be able to test. Would it be worth writing extra scripts in .../test/ so that we can=20 re-test easily after bug fixes and before future releases? Or would=20 that be more effort than it is worth? > The next step would be devoting ourselves to quickly handling > bugs that come in from users from some specified period and release > '3.2.1'. I put this in so we don't leave all this work up to > Gilles, our devoted maintainer of 3.1.X. Hear, hear!! > Formal testing is yucky and delays us stamping it 3.2-final, but > I'd rather spend a month doing this than see silly errors found by > a score of endusers. Absolutely. > The next step would comming up with a test plan, basically a list > of test points so we can divvy up the work. This needs to be > complete by next weekend. Aye, Aye, Cap'n! Lachlan --=20 lh...@us... ht://Dig developer DownUnder (http://www.htdig.org) |