Rick Hillegas wrote: > What I meant by "fork" is that we could introduce a new subdirectory > under org/apache/derbyTesting as Myrna suggested. Then, as tests were > converted to JUnit, we could move them from their old location to a new > location under the JUnitTests subdirectory. Moving would involve > svn-moving the test, which means that the old version would disappear > from the code tree. There would be only one version of the test in the > code tree. I agree that maintaining two independent copies would be a > bad idea.
Sounds great. It's just that "fork" has a specific, evil, meaning in the open source world, that is not related to what you are doing. So, please, just don't use fork to describe this, more like migrate, move or convert. Dan.
