A wise old hermit known only as Vincent Harcq <[EMAIL PROTECTED]> once said:
> No, You fixed it or maybe somebody else ? > I like to put names because on the SF Bug tracking list I see directly > where work is needed. > After opening 5 times a Fixed bug (well yes I have a poor memory ;) ) I > begin to do some boxing with my keyboard. > > BTW, The rule now is we put Resolution FIXED when the bug is fixed and > Status CLOSE it at release time. > > Why not put the Status to PENDING, the list is then a lot shorter and my > keyboard will survive. > Then Query all PENDING issues at release time and you have the > CHANGES.TXT. That wouldn't work - Pending items are automatically deleted after 14 days (unless someone comments further on them, in which case they're reopened). I think the current method's fine; it makes it easy to spot the ones that have been done for a release a) for adding to the changes.txt and b) for verifying the fix for QA (preferably by whoever raised them, certainly by someone other than the person that fixed them, and ideally including a unit test to detect regressions). However, in practise I'm not sure they ever get checked... Easiest thing is for whoever fixes it (or is working on it) to make sure they assign it to themselves, so you can tell which ones still need doing. I don't mind if we start closing them once they've been verified, though. I can always hang on to the automatic mails it sends to the list, and update the changes.txt from those (only snag would be if my machine broke down and I lost them...) Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
