On 14-01-11 12:58, Peter Firmstone wrote:
I'm all for development on the trunk. Stabilisation can take place in
a branch.
I believe I fell foul of that mistake not so long ago, I'd been
developing in trunk, only to discover that quite a number of tests
weren't run by qa.run, the changes had to be reverted and development
continued in skunk.
After that I believe the consensus was to develop in skunk and then
bring / merge code into trunk.
No, what we had was:
- integration of the total QA
- QA finding bugs
- Reverts of some of your changes
- QA finding less bugs, still not perfect due to QA.
The missing step was here, reintegrating your changes, in a stepwise
manner, reviewing and checking if the total QA result stayed the same.
correct?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
