On Mon, 2007-05-28 at 12:43 +0800, Ed Greshko wrote: > It is much more time saving to test each beta individually and then when you > have your final RC test an upgrade from a formal previous release to a > formal final release or final RC. If any problems are found at that point > you fix those and then release. > > It is inefficient to resolve upgrade issues in multiple beta stages that may > or may not exist when you get further down the line. OK, if I understand you, you're saying you should test each beta separately, as a "by itself install" until you get to an RC, and then test the official upgrade from official release to RC? Cause if that is the case, you leave little room for error, or not enough time to get anything fixed (especially if it's a bug and you have to wait on someone else to fix) if you have problems. At least during the betas, you start testing and start getting things fixed way ahead of time and insure they are fixed, both on the user end and the developer end. I guess if you have the time and not in a hurry to upgrade, then you can just wait and start testing when the RC's come out, get problems fixed and/or resolved, then do the official upgrade. Guess depends on your time restraints, priorities, and what you need to do the job. -- Mike Chambers Madisonville, KY
