Hi, Sorry for the late response.
On Dec 17, 2007 12:45 PM, Mark Brouwer <[EMAIL PROTECTED]> wrote: > As you mention "Almost all normal development can and should happen > within the trunk in cooperation with other developers", do you have a > good suggestion to find out who is working on which versioned objects > given SVN as our SCM. I typically use the assignee field in Jira to get an overview on who's currently working on which feature. Another good source of this information are the svn commit logs (including the commit messages sent to -commits). While there are locking and other similar features in svn, they are typically not used in open source projects. Its much better to just commit your changes than to declare that you're still working on it and that others should avoid touching that part of the codebase. This way everyone just needs to check that their changes are compatible with the latest svn trunk instead of whatever changes other people may be working on. A good practice is never to have more than a single day of coding effort uncommitted (or uploaded for review as a patch). This forces you to break down larger efforts into small, reversible steps that are also much easier for others to review and comment on. Such small changes also streamline the development process by making commit conflicts rare and reducing the need for complex merging and integration work. > Given the large amount of scheduled and assigned issues for AR2 I think > there is a significant amount of overlap with versioned objects already, > I and others could publish a list of all files being touched but > otherwise I can't come up with an idea to let others know what I'm touching. This is exactly why I'd like to see that activity already happening in svn trunk. The very purpose of an SCM is to help people work together on the same codebase, and there is no need for us to reinvent tools for doing that. BR, Jukka Zitting
