+1
Two more suggestions...
1. ALL modifications should be tied to a JIRA ticket. So even if you're working on something that is totally on your own initiative, please make a JIRA issue and assign it to yourself.
2. If for some reason you feel the need to comment out a section of code, please also write a comment about why you're doing that and the curcumstances under which the code could be uncommented or deleted. It's really unnerving to come across large sections of commented code - could they be uncommented at some point in time? BTW - my own personal bent is that you should never comment out code except in testing scenarios. If it's not needed, then delete it. If you need to get it back then use your SCM to retrieve the history.
Jeff Butler
On 6/6/06, Brandon Goodin <[EMAIL PROTECTED]> wrote:
Hey All,
Just a friendly reminder. Let's be sure that we are using JIRA to
communicate with each other. When you are working on a bug be sure to
assign it to yourself, adjust the status, and maintain this
information through the various stages of resolution. Also, it is good
to use JIRA to record questions and answers regarding the bug. This
will help us in the future as we are working through other issues. It
is best to keep the bug information as full as possible. This will
avoid us having to search development archives for information that
can more easily be found in bug comments.
Thanks!
Brandon Goodin
