Issuezilla contains many items that are not bugs but are change requests. If we consider an issue to be a true bug we make sure it is classified as a "Defect".
The subcomponent then narrows down which source component is the likely area where change is needed to resolve the defect. One defect may possibly cover many component in which case we choose the one with the biggest impart or we create multiple issues. Regards Bob On 6 April 2011 05:13, McLovin <[email protected]> wrote: > Hello, every one! > I'm researching the AugoUML project on some topics about the relationship > between it's bugs and source code. > I've already got the "augouml-log.xml" and a lot of bug-reports such as > "180.xml". > Thus, my question is how I can find out their relationship. As we all know, a > bug may relate to some source code files, and one code file may relate to > some bugs as well. However, the bug-reports just describe the bugs' > information, and the "augouml-log.xml" just describe the logs' information. > These logentries may not be about bugs. > > Could you do me a favour? > Thanks very much!!! ^_^ > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2717284 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. > To be allowed to post to the list contact the mailing list moderator, email: > [[email protected]] > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2717418 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
