[Hyrum K. Wright]
> A number of API changes would be frozen for the intermediate 1.5
> release, and those APIs may need to be rev'd to support merge
> tracking changes. I don't see this as a major drawback, though.
Is it practical to look for APIs revved in trunk and again in branches/
merge-tracking, and merge those bits to trunk _before_ branching 1.5.x?
I'm not saying the merge-tracking branch is _done_ revving APIs, but
this may reduce the 1.6 API churn considerably.
I understand it may not be possible in all cases, due to new data
structures that are only meaningful with merge tracking.
Received on Sun Mar 11 04:38:10 2007
This is an archived mail posted to the Subversion Dev