Well there are a lot of answers for how researchers do this, and it will depend on the data source and intent of the project.

1. For background on what others have done, I'd recommend starting with flosshub.org paper database in addition to your normal literature search tools such as Google Scholar or ACM dl.

We have the tags 'bug reports' for example and a long list of papers to be downloaded there:
http://flosshub.org/category/tags/bug-reports

Keep in mind that any papers on flosshub are about FLOSS - there are many other uses of bug reports for making non-FLOSS software but the ones on flosshub have to have something to do with FLOSS.

2. The MSR conference covers this topic regularly. I'd recommend searching their archives. Many of the (FLOSS-oriented) papers from MSR are on the flosshub site. Each year the MSR hosts a "challenge" for mining. Many of these papers cover bug trackers and related issues.

3. SRDA has some bug information about projects on sourceforge. http://zerlot.cse.nd.edu/mediawiki/index.php?title=Main_Page

4. Once you get a data set, FLOSSmole would be happy to host it for you. Contact me for more details on how we can help you store your data.

-megan




On Wed, Apr 3, 2013 at 6:47 AM, <akande@sce.carleton.ca> wrote:
Dear All,
Am a new researcher in the field of mining software repositories, and
i want clarifications on this:
How to extract from bug repositories.
I will be grateful to have an explicit reply.
Thanks



------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Ossmole-discuss mailing list
Ossmole-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ossmole-discuss