Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Mike Wake wrote: > Is the intention of this concept to be used like a mini branch per bug. > This would be great to allow developers to further isolate themselves > from each other while still having the ability to checkin incremental > changes to the repository without the overhead/mess created by applying > a branch to their whole working area. A branch per bug would be nearly impossible to manage over any length of time - you could easily end up with thousands of them. Merging would become a real headache. CVS already handles multiple developers working on the same code extremely well, so there's no need to invoke branches here. Marking the changes by bug is useful for tracking (there's still some extra functionality to be added for this) and will allow you to associate changes to the repository to specific active bugs eg. in bugzilla. With the appropriate UI it should be easy to see who's working on what, and any changes that they have made. If you want to keep separate lines of development (active/testing/release) a branch can do this with a trigger script to push code automatically from active->testing based on specific criteria eg. a special commit message. Bug IDs probably don't help much here though as you can have several developers working on the same file and there won't be a clear distiction between one bug and another. Tony