Hi Stefan, I'm not a committer to the project, but I've worked on other projects with svn and JIRA. If you use the Eclipse, there's a plugin called Mylyn that you can use that makes this process a little easier. As you work on an issue, Mylyn keeps track of the files that you worked on (called a context or change set). To commit all changes for a particular issue, you simply open the issue in Eclipse, and commit the files that you see listed under the Context tab. You can also attach the context to the issue, this makes it easier if the issue is reopened in the future, since Mylyn automatically reopens all files that are in the attached context -- so somebody can pickup where you left off. You can see a demo of this here:
http://www.redmonk.com/cote/2007/12/11/the-jira-connector-for-mylyn-demo/ Hope this helps, Mark On Tue, Feb 3, 2009 at 9:14 PM, Stefan Bodewig <bode...@apache.org> wrote: > Hi all, > > since I'm sort of a new commons committer (technically I've always > been, I've just not used it much) I'm unsure whether there is a policy > of how you connect svn commits and JIRA issues around here. > > So far I've named the JIRA issue in the commit message and noted the > svn revision inside a comment to the JIRA issue. Is there anything > else I should have done like adding an explicit link to the svn > revision in JIRA (bugzilla adds them automatically nowadays)? > > Thanks > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- Mark Fortner blog: http://feeds.feedburner.com/jroller/ideafactory
