[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-ui-dev] Commit comments
|
For an internal bug tracking system, we have a link from the bug entry that brings up a list of all the files committed as part of fixing that bug. I find it very handy for these kinds of questions. The list shows a sortable table with an entry for each file touched including the path, filename, date/time, branch and revision, user name, and commit comments. The filename and branch/revision are links to the CVS web.
Maybe something similar could be done at Eclipse? If everybody put "bug nnn" in the comment, it could key off that. Hmm... a quick Google search tells me that this has been done before. Generally they work by putting comments in the bugzilla entry when you push a file. That might be better than what we did because it would keep everything in one place and also notify the cc'd people. See:
http://www.faqs.org/docs/bugzilla/integration.html
http://www.einval.com/~steve/software/cvs-bugzilla/
http://www.linuxdevcenter.com/pub/a/linux/2003/06/05/scripts.html
http://www.cvszilla.org/
http://kered.org/article-2004.04.09-cvs_bugzilla_integration.html
http://www.public.asu.edu/~makrists/scmbug/latest_manual/html/index.html
http://projects.edgewall.com/trac/ (Subversion)
http://www.atlassian.com/software/jira/docs/latest/cvs_integration.html (Jira)
> -----Original Message-----
> From: platform-ui-dev-bounces@xxxxxxxxxxx
> [mailto:platform-ui-dev-bounces@xxxxxxxxxxx] On Behalf Of Nick Edgar
> Sent: Friday, April 29, 2005 4:10 PM
> To: Eclipse Platform UI component developers list.
> Subject: Re: [platform-ui-dev] Commit comments
>
> I'm all for (1). (2) is OK if necessary, but the bug report should have
> a description of the work done, and the commit comment time and bug
> comment time can usually be correlated.
>
>
