Proceedings of the 13th International Conference on Mining Software Repositories 2016
DOI: 10.1145/2901739.2901751
|View full text |Cite
|
Sign up to set email alerts
|

Using dynamic and contextual features to predict issue lifetime in GitHub projects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
49
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
6
2

Relationship

1
7

Authors

Journals

citations
Cited by 59 publications
(49 citation statements)
references
References 24 publications
0
49
0
Order By: Relevance
“…However, there are also studies that rely on different metrics and methodologies to select GitHub projects. issues and commits to obtain a large set of GitHub projects and study models to predict whether an issue will be closed [44].…”
Section: Related Workmentioning
confidence: 99%
“…However, there are also studies that rely on different metrics and methodologies to select GitHub projects. issues and commits to obtain a large set of GitHub projects and study models to predict whether an issue will be closed [44].…”
Section: Related Workmentioning
confidence: 99%
“…The problem of predicting remaining time has also been extensively studied in the context of software development processes. For example, Kikas et al predict issue resolution time in Github projects using static, dynamic, and contextual features. A later work by Rees‐Jones et al further emphasizes the importance of contextual features for predicting issue lifetime in Github projects.…”
Section: Related Workmentioning
confidence: 99%
“…We chose this period of time because GHTorrent started data collection in 2012, and we need to collect about 10,000 projects (considering about the work load). Then, we deleted projects that are forks (recommended by [17,18]) and obtained 8,638 samples. In addition, we deleted projects that are not described in English or have been removed.…”
Section: A Standard Datasetmentioning
confidence: 99%