Step 1: To manually identify the goldset, first, we run a script to randomly select the 25 bugs that were in `FIXED' status from four representative OSS projects as depicted in Table REF  and detailed in Section REF . (Note that, we deemed that this number of bugs was sufficient for performing a synthetic study that required extensive manual analysis of goldset data. Likewise, the analysis of the results from multiple combination of approaches (i.e., configurations); This sample was also comparable to other studies [1]}, [2]}). Then, for each bug, we identified the bug-fixing comment(s) in the discussion threat that provided the actual fix of a bug—we flagged that comment or a set of comments to be as our goldset. In general, a comment that represents a clue or indicates a bug fix includes the revision link, attached patches, resolution steps or possible links to other duplicate bugs [3]}, [4]}, [5]}. The revision alone may also include specific file names with their corresponding method signatures and explanations why changes were made. To make the final decision about the goldset, first author and a junior researcher resolved the conflicts of relevance using an established well-known majority–voting mechanism [6]}, [7]}. Finally, the most highly voted comments were added in the goldset. In Table REF , the goldset is denoted by `Bug ID'.
