Sure, but my only concern is many svn log analysis tools will only display the
first line of a commit message, so I think it should contain some sort of
summary. As for Contributed By, I was thinking only to put that there if there
was a patch, because otherwise, it is easy to scrape the reporter from the
ticket itself.
BTW, +1 for using a format that JIRA can understand for bugs, even if we aren't
using it currently.
Don
Ted Husted wrote:
On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote:
There was in the CVS days, and I don't believe I've seen it since. I'm thinking
something simple like:
Adding this new feature
PR: 234
Type: (fix, add, update, documentation)
Contributed By: Sarah Jones
I'd suggest somthing like this:
----
Bug 5739
* Struts fails silently in too many places
* Reporter: Frank Lawlor
* Add error messages for ..
* ...
----
This format follows the text on the bugzilla screen, and it's
compatible with the way JIRA hooks up issues to Subversion commits, in
case we ever go there. Following the way JIRA/Subversion works, f a
commit applies to multiple tickets, all the IDs should be listed
first.
---
Bug 5739
Bug 9616
* Struts fails silently in too many places
* Make error keys more specific
* Reporter: Frank Lawlor, David M. Karr
* Add error messages for ..
* ...
----
I would suggest not making the words "Contributed by" part of a
standard template, because sometimes "contributed" might be too strong
a word for the reporter's role. There are many cases where someone
might report an issue or request a feature, but we still do the actual
coding.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
