On 1/31/07, Mark Brouwer <[EMAIL PROTECTED]> wrote:
3) merge ServiceUI and JTSK for the time being so we have one build
process,
4) work towards an initial (internal) release that in all aspects
compatible with the current JTSK
5) setup of test infrastructure to validate the outcome of 4
For what it's worth, in order to achieve 4) it would seem that
doing 5) before 3) might be advisable.
I realize some folks are very anxious to start modifying the
baseline JTSK codebase that was contributed as soon as
possible; taking it in new directions and/or "fixing" all the
problems they perceive it to have. But given that there is an
existing and somewhat complete set of tests, along with a harness
for running those tests, I would think that it might be desirable
to establish a baseline by first getting that mechanism set up
and running before combining or modifying the initial codebase.
That way, when people do start changing the existing code,
they'll have a point of reference as well as a mechanism for
measuring the quality of their changes.
Just my 2 cents (euros?, rubels? ...),
Brian
