Hi,
On Wed, Feb 4, 2009 at 6:30 AM, Rahul Akolkar wrote:
> Due to this, noting the svn revision in a comment to the JIRA issue
> can be considered optional (its good practice nevertheless).
+1 on it being good practice
Including the relevant revision number in a Jira comment can come in
really
On 2009-02-04, Mark Fortner wrote:
> 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.
Thanks for the pointer Mark.
I've read about Mylyn a
On 2009-02-04, Rahul Akolkar wrote:
> On Wed, Feb 4, 2009 at 12:14 AM, Stefan Bodewig wrote:
>> 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
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
On Wed, Feb 4, 2009 at 12:14 AM, Stefan Bodewig 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 J
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
