Hi Akara,
I haven't tried, but if you ping infrastructure at apache dot org,
they can probably tell you what is needed.
Craig
On Jan 27, 2009, at 1:03 PM, Akara Sucharitakul wrote:
Craig,
I don't seem to get fisheye to work for me. Any pointers? Thanks.
-Akara
Craig L Russell wrote:
Just a suggestion: you might see if all of the closed JIRA issues
have the subversion commit notices. Those that don't would be
candidates for manually adding a comment with the commit (and
possibly a link to the diff via fisheye).
Craig
On Jan 27, 2009, at 11:04 AM, Akara Sucharitakul wrote:
No need. JIRA links that automatically.
Try go to issue OLIO-3 using JIRA. Below, you'll see a number of
tab-like hyperlinks with these items:
All Comments Work Log Change History Subversion Commits
FishEye
Click on Subversion Commits and you'll see the commit message and
hyperlinks to the diffs on the commit. All you need to do is to
put the issue numbers into the svn commit message. My standard
format is "Fix for issue OLIO-3 [, ...]" and then I add further
comments to the commit message. Hope this makes you happier.
-Akara
Shanti Subramanyam wrote:
It would be great to include the svn commit message (including
the patch) in the resolution of the JIRA issue. It's just a
matter of cut-n-paste from the email that the svn commit sends
out. This helps one see at a glance which files were changed and
the nature of the changes.
Thanks
Shanti
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
