On 9/1/2010 12:22 AM, Sim IJskes - QCG wrote:
On 09/01/2010 01:16 AM, Jonathan Costers wrote:
Similarly, having backed out the RemoteEvent changes, and running the
"discoveryservice" category:
It looks to me, that the code in the trunk was not completely ready.
Would it be a good idea to revert the changes until the unit tests run
again, and build a branch in svn to continue the work?
If a committer (with svn access) needs help, i can offer some assistance.
I'm still waiting for my Apache account to be created, so I'm currently
a committer without svn access, but I'm interested in advice on how to
manage branches in an Apache context.
I like to check in early and often, but my TaskManager performance
project has an experimental aspect to it. The TaskManager changes should
increase concurrency, which may shake out bugs in other code, as well as
having their own risks. Only benchmarking can prove that a change
improves performance - intuition and experience are notoriously
unreliable predictors.
The TaskManager changes should be tested against all runnable tests
before being checked into the trunk, but that can only be done if they
are based on a version that passes all runnable tests.
That all seems to me to be a job for branches.
Patricia
