Re: tree-conflicts: patch for improved cmdline tests

"Mark Phippard" <markphip_at_gmail.com> writes:
> It does not make sense to me that if you are developing a new feature
> on a branch, you would write the tests for this feature on trunk.
> Isn't that kind of burdensome and unnatural for the developer?

Depends on the test. If it tests only something new on that branch,
then yeah. But if it's a test about something that also exists on
trunk, then it should start life on trunk.

I guess I'm mixing up two unrelated issues. One, it worries me that the
tree-conflicts branch has spent so much time off trunk (this is
something that worries stsp, julian, et al, too I think). Two, on a lot
of branches I see changes (sometimes including tests) that could be made
on trunk get made on the branch instead.

So sure, if the test is completely branch-specific, then commit it to
the branch. But let's also try to get that branch into trunk sooner
rather than later! It doesn't have to be perfect to be merged.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-19 16:55:05 CEST