On Tuesday 06 January 2004 05:48, Leo Simons wrote:
> > 2) how should we start refactoring Merlin to make it what we
> > all need?
> > * please note that development should be able to continue
> > while refactoring occurs.
>
> = Step 0 =
>
> is a feature freeze. Not code freeze, feature freeze. Development can
> continue, but no new features. None.
Sarcasm;
* Feature freeze.
* Fix these outstanding problems.
* High resistance mode
* Fix critical remaining problems.
* Hand over to QA.
* Functional Testing
* Fix revealed flaws
* Execute User Acceptance Test
:
:
You start sounding like a demanding Corporate Manager :D
It doesn't suit you...
More Seriously;
Step 0 is "difficult to define", as how much needs to be "started" to be
considered "inside" the freeze.
Step 1. I (and I think Stephen) agree whole-heartedly.
Step 2, 3. Step 1 over-whelms me already...
May I suggest a slightly different 1,2,3;
Step 1. Write a test.
Step 2. Refactor a "smell".
Step 3. Document.
Step 4. Goto Step1.
("smell" being all the stuff Leo brings up).
> I don't even come close to having the time or the energy to do a
significant part of that.
Of course, you are the manager, and they never have time for anything :o)
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
