-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This IS working. That was my point. But it only "works" if mention of the issue is made in the commit log. JIRA <- SVN log works great so this is a tap-dev process to make sure it happens, not infra.
Howard Lewis Ship wrote: > I believe this was working in the past (or was that for HiveMind). In > any case, yes, +1, this is very very useful and important. May need > to add an INFRASTRUCTURE bug to get it properly set up. > > On 5/7/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > I could have sworn there was a page on the Wiki about this, but I sure > can't find it anywhere now. So.... > > After a message posted on the Cayenne list to this effect, I checked and > Tapestry also has SVN linked into JIRA (or vice-versa depending on how > you look at it). This means when you're viewing an issue, you can click > the SVN Commits tab and see all the files touched because of that issue > (okay - when used properly :-)). I'd like to propose making this > standard practice so we can really see why things are changing. [Yes, > I'm big on "don't touch unless there's a reason" - where, for Tapestry, > "reason" == "JIRA issue"] I've tried to have all commit msgs in the form: > [TAPESTRY-XXX] What I did > and they are properly linked in the issue. > > This does mean breaking commits down a bit - no more "lump changes", but > it does help in tying changes to reasons. > > [And if anyone knows the page on the Wiki I mentioned at the beginning, > could you send me a link to it?] > > Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEX3KGaCoPKRow/gARAo7rAKCiD7m6RPEwMmtk3AAIdBI3oH6GdwCePNqm RP3nDOtOwQhFTPlCVXVvDM4= =PNtN -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
