Re: Prototype design for merge tracking in Subversion

This sounds like a typical conflict beween "top down" and "bottom up"
approaches to writing software. Do you spend weeks in theoretical
discussion and design documents, then code at the very end? Or do you
hit the ground coding, dissect the results, code again, dissect, etc.
until you arrive at a design?

While you're certainly welcome to start coding mockups of merge or
history-tracking behaviors, I think what Branko's trying to say is
that historically, this project has always been dominated more by the
"top down" sorts of people. We much prefer to spend two months
discussing theoretical frameworks before we write any code at all. I
think you're likely to get more participation and general engagement
if you take that route.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 13 15:22:56 2006