Ryan Hoegg <[EMAIL PROTECTED]> writes: > Daniel Rall wrote: > > >Sounds like I'm not the only outsider interested in this code! How > >about a short-lived CLIENT_REFACTORING branch in CVS? We could give > >Ryan commit access, and you guys could proceed with the development > >from here on out in ASF CVS. Everyone would be free to comment, and > >we can merge into the mainline when you think things are ready. I'd > >be happy to help with any CVS/branching/merging issues. Thoughts? > > > Well we are having a bit of a feature creep here. It is no longer > just CLIENT_REFACTORING as we are looking at abstracting the transport > layer for the XmlRpcServer code as well. I would be interested in > having this code up in CVS somewhere, although I've never worked with > CVS branches before.
Working with branches mostly involves appending -rBRANCH_NAME to your cvs checkout and update commands. Eventually, you learn how to use update -j to merge branches together. > Another thing I'm not sure about is design documentation. Sometimes > it helps me to draw up larger refactorings like this one in quasi-UML > so I can see the bigger picture. If I do this, do I store the > .VSD/.PNGs in CVS somewhere? Where? It would be nice to have them as > a resource when we are talking over some of the design decisions we > are making. Yes, they should live in the repository, possibly under xdocs/ (assuming they have associated content). -- Daniel Rall <[EMAIL PROTECTED]>
