: E.g., yesterday someone opened a bug report on CPAN's RT system. There was no : actual patch, but a suggested fix in the narrative. I applied a fix. I commented : on the RT ticket to that effect. : : Should I also have opened a JIRA ticket? I'm lazy. I'd prefer not to. I : referenced the RT ticket in my svn commit message, because as I saw it, that : constituted an adequate audit trail considering there was little question of IP : conflict. Was that adequate? I dunno. Hence, this thread.
I don't follow the lucy commit list so i'm not familar with the specifics of this example, but... personally i think any "bug" should be filed in jira, regardless of how trivial it is to fix, because that way there is a clear record of it that is easy to see if someone else gets burned by the same bug and goes seraching in the "official" place to seach for bugs to see if it's already been reported/fixed. Filing a Jira for all bugs seems particularly important for Lucy since the CHANGES.txt in the releases is built from the Jira changelog feature -- so if a bug fix isn't in Jira, it doesn't even get listed in the CHANGES.txt, so users never know that you fixed it (or to be wary of that bug in older versions if they choose not to upgrade, or to sanity check that the fix doesn't have side affects that burn them in some particular use case, etc....) But beyond that, even for projects that manage CHANGES.txt manually (or build from svn commit logs instead) a Jira issue becomes hte focal point for discussing that bug, discussing the fix (should there be subsequnet discussion about alternative fixes, larger ramifications, regression in future versions) and a place for people who have not yet (or can not) upgrade to the fixed version to ask questions about ramifications and workarrounds, etc... if you only refrence the third-party tracker URL where you heard about the bug in the commit message for the fix, then you have implicitly suggested that that third-party tracker is an appropriate place people should go for more information about that bug, which diminishes the cohesion arround the official Jira system and contributes to fragmentaation in discussions surrounding the project -- which is going to happen anyway, not reason to enourage it. That's for "bugs" ... for "new features" i would make the same arguments. However: if someone on some blog, or stackoverflow tread, or CPAN RT issue, or IRC channel, or the lucy-user list, points out a simple typo, confusing doc paragraph, minor optimization, clearer way to do something in the build scripts, or suggests a new test case -- then maybe a Jira isn't really required. But that's just my opinon -- personally i file a jira for *EVERYTHING* -Hoss
