This one time, at band camp, Thomas Yip said:
TY>The list you come up gives good ideas on what
TY>could be included. But, I afraid it would be far too
TY>much work, if it is what "must" done and if I am
TY>the only one doing it. Likely, I am the only one.
TY>
TY>I think it is much more practical for me to find
TY>two hours and fill the bugzilla at once for all items.
TY>Spending an hour each, means the list will only be
TY>finished in months later. For instance, listing
TY>possible approaches may require me to look at
TY>the code for half an hour each already.
I agree that Werner's list is good. However, I agree with Thomas
that he cannot spend time other than putting in quick information
about the defect. As developers work on defects, they need to
continually update Bugzilla with their findings. This will allow
us to know who is working on what as well as to track progress on
a defect.
Here's a quick example:
1) I start to work on defect XYZ.
2) I have to stop before I actually fix the defect because it's
too late at night to continue.
3) I log any relevant findings about the defect into Bugzilla
(e.g. how to reproduce it, steps I took in the debugging
process that got some results, etc.).
This will allow me or *anyone else* to pick up where I left off
with my investigation into defect XYZ.
Thomas, if you could just enter the defects into Bugzilla for now
that would be great!
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
