On 29-11-12 12:34, Peter Firmstone wrote:
I think that's wise equally I'm pondering how you cope with trunk
moving on
and breaking a bunch of your tests for which there would be fixes in the
trunk test suite. Are you happy doing merges as and when or ???
I'm not sure, at this point I just know we've got problems, there's a
lot of coupling in the test suite and a lot of shared state; it's all
based on inheritance.
There are two test types:
How about the following, we develop on a branch. Then we merge or patch.
We release. We pull a new branch of trunk. We merge/patch stuff that did
not make it in the release from the previous dev branch into the current
dev branch. (we can skip rebranching if we want to keep the old dev branch).
It looks like a lot more work, but i suspect river-core will only get
small changes, and the rest will end up in other subprojects.
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
