book.bib

%% Place TeX-style references in this file.

@inproceedings{mujahid2017examining,
  title={Examining user complaints of wearable apps: a case study on android wear},
  author={Mujahid, Suhaib and Sierra, Giancarlo and Abdalkareem, Rabe and Shihab, Emad and Shang, Weiyi},
  booktitle={Mobile Software Engineering and Systems (MOBILESoft), 2017 IEEE/ACM 4th International Conference on},
  pages={96--99},
  year={2017},
  organization={IEEE}
}

@article{hassan2018studying,
  title={Studying the dialogue between users and developers of free apps in the Google Play Store},
  author={Hassan, Safwat and Tantithamthavorn, Chakkrit and Bezemer, Cor-Paul and Hassan, Ahmed E},
  journal={Empirical Software Engineering},
  volume={23},
  number={3},
  pages={1275--1312},
  year={2018},
  publisher={Springer}
}

@article{mcilroy2017worth,
  title={Is It Worth Responding to Reviews? Studying the Top Free Apps in Google Play},
  author={McIlroy, Stuart and Shang, Weiyi and Ali, Nasir and Hassan, Ahmed E},
  journal={IEEE Software},
  volume={34},
  number={3},
  pages={64--71},
  year={2017},
  publisher={IEEE}
}

@phdthesis{mcilroy2014empirical,
  title={Empirical studies of the distribution and feedback mechanisms of mobile app stores},
  author={Mcilroy, Stuart},
  year={2014}
}

@misc{appNumber,
  author = {Statista},
  title = {Number of apps available in leading app stores as of 1st quarter 2018},
  year = 2018,
  howpublished = {\url{https://www.statista.com/statistics/276623/number-of-apps-available-in-leading-app-stores}},
  note = {Accessed: 2018-10-10}
}

@misc{appStoreLaunch,
  author = {AppleInsider},
  title = {Apple's App Store launches with more than 500 apps},
  year = 2008,
  howpublished = {\url{http://appleinsider.com/articles/08/07/10/apples_app_store_launches_with_more_than_500_apps}},
  note = {Accessed: 2018-10-10}
}

@misc{androidMarketLaunch,
  author = {Melissa Perenson},
  title = {Google Launches Android Market},
  year = 2008,
  howpublished = {\url{https://www.pcworld.com/article/152613/google_android_ships.html}},
  note = {Accessed: 2018-10-10}
}

@article{scoccia2018investigation,
  title={An Investigation into Android Run-time Permissions from the End Users’ Perspective},
  author={Scoccia, Gian Luca and Ruberto, Stefano and Malavolta, Ivano and Autili, Marco and Inverardi, Paola},
  year={2018}
}

@article{palomba2018crowdsourcing,
  title={Crowdsourcing user reviews to support the evolution of mobile apps},
  author={Palomba, Fabio and Linares-V{\'a}squez, Mario and Bavota, Gabriele and Oliveto, Rocco and Di Penta, Massimiliano and Poshyvanyk, Denys and De Lucia, Andrea},
  journal={Journal of Systems and Software},
  volume={137},
  pages={143--162},
  year={2018},
  publisher={Elsevier}
}

@inproceedings{wei2017oasis,
  title={OASIS: prioritizing static analysis warnings for Android apps based on app user reviews},
  author={Wei, Lili and Liu, Yepang and Cheung, Shing-Chi},
  booktitle={Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering},
  pages={672--682},
  year={2017},
  organization={ACM}
}

@inproceedings{palomba2017recommending,
  title={Recommending and localizing change requests for mobile apps based on user reviews},
  author={Palomba, Fabio and Salza, Pasquale and Ciurumelea, Adelina and Panichella, Sebastiano and Gall, Harald and Ferrucci, Filomena and De Lucia, Andrea},
  booktitle={Proceedings of the 39th international conference on software engineering},
  pages={106--117},
  year={2017},
  organization={IEEE Press}
}

@inproceedings{jha2017mining,
  title={Mining user requirements from application store reviews using frame semantics},
  author={Jha, Nishant and Mahmoud, Anas},
  booktitle={International Working Conference on Requirements Engineering: Foundation for Software Quality},
  pages={273--287},
  year={2017},
  organization={Springer}
}

@inproceedings{li2017crowdsourced,
  title={Crowdsourced App Review Manipulation},
  author={Li, Shanshan and Caverlee, James and Niu, Wei and Kaghazgaran, Parisa},
  booktitle={Proceedings of the 40th International ACM SIGIR Conference on Research and Development in Information Retrieval},
  pages={1137--1140},
  year={2017},
  organization={ACM}
}

@article{hu2018studying,
  title={Studying the consistency of star ratings and reviews of popular free hybrid Android and iOS apps},
  author={Hu, Hanyang and Wang, Shaowei and Bezemer, Cor-Paul and Hassan, Ahmed E},
  journal={Empirical Software Engineering},
  pages={1--26},
  year={2018},
  publisher={Springer}
}

@inproceedings{ali2017same,
  title={Same app, different app stores: A comparative study},
  author={Ali, Mohamed and Joorabchi, Mona Erfani and Mesbah, Ali},
  booktitle={Proceedings of the 4th International Conference on Mobile Software Engineering and Systems},
  pages={79--90},
  year={2017},
  organization={IEEE Press}
}

@article{li2017mining,
  title={Mining User Reviews for Mobile App Comparisons},
  author={Li, Yuanchun and Jia, Baoxiong and Guo, Yao and Chen, Xiangqun},
  journal={Proceedings of the ACM on Interactive, Mobile, Wearable and Ubiquitous Technologies},
  volume={1},
  number={3},
  pages={75},
  year={2017},
  publisher={ACM}
}

@inproceedings{anchieta2017exploring,
  title={Exploring Unsupervised Learning Towards Extractive Summarization of User Reviews},
  author={Anchi{\^e}ta, Rafael T and Moura, Raimundo S},
  booktitle={Proceedings of the 23rd Brazillian Symposium on Multimedia and the Web},
  pages={217--220},
  year={2017},
  organization={ACM}
}

@inproceedings{panichella2016ardoc,
  title={Ardoc: App reviews development oriented classifier},
  author={Panichella, Sebastiano and Di Sorbo, Andrea and Guzman, Emitza and Visaggio, Corrado A and Canfora, Gerardo and Gall, Harald C},
  booktitle={Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering},
  pages={1023--1027},
  year={2016},
  organization={ACM}
}

@inproceedings{gao2018online,
  title={Online app review analysis for identifying emerging issues},
  author={Gao, Cuiyun and Zeng, Jichuan and Lyu, Michael R and King, Irwin},
  booktitle={2018 IEEE/ACM 40th International Conference on Software Engineering (ICSE)},
  pages={48--58},
  year={2018},
  organization={IEEE}
}

@inproceedings{simmons2016agree,
  title={Agree to disagree: on labelling helpful app reviews},
  author={Simmons, Andrew and Hoon, Leonard},
  booktitle={Proceedings of the 28th Australian Conference on Computer-Human Interaction},
  pages={416--420},
  year={2016},
  organization={ACM}
}

@inproceedings{i2017crowdsourced,
  title={Crowdsourced App Review Manipulation},
  author={Li, Shanshan and Caverlee, James and Niu, Wei and Kaghazgaran, Parisa},
  booktitle={Proceedings of the 40th International ACM SIGIR Conference on Research and Development in Information Retrieval},
  pages={1137--1140},
  year={2017},
  organization={ACM}
}

@inproceedings{chen2017toward,
  title={Toward detecting collusive ranking manipulation attackers in mobile app markets},
  author={Chen, Hao and He, Daojing and Zhu, Sencun and Yang, Jingshun},
  booktitle={Proceedings of the 2017 ACM on Asia Conference on Computer and Communications Security},
  pages={58--70},
  year={2017},
  organization={ACM}
}

@inproceedings{xie2016you,
  title={You can promote, but you can't hide: large-scale abused app detection in mobile app stores},
  author={Xie, Zhen and Zhu, Sencun and Li, Qing and Wang, Wenjing},
  booktitle={Proceedings of the 32nd Annual Conference on Computer Security Applications},
  pages={374--385},
  year={2016},
  organization={ACM}
}

@article{nayebi2018app,
  title={App store mining is not enough for app improvement},
  author={Nayebi, Maleknaz and Cho, Henry and Ruhe, Guenther},
  journal={Empirical Software Engineering},
  pages={1--31},
  year={2018},
  publisher={Springer}
}

@article{martin2015survey,
  title={A survey of app store analysis for software engineering},
  author={Martin, William and Sarro, Federica and Jia, Yue and Zhang, Yuanyuan and Harman, Mark},
  journal={IEEE transactions on software engineering},
  volume={43},
  number={9},
  pages={817--847},
  year={2017},
  publisher={IEEE}
}

@article{genc2017systematic,
  title={A systematic literature review: Opinion mining studies from mobile app store user reviews},
  author={Genc-Nayebi, Necmiye and Abran, Alain},
  journal={Journal of Systems and Software},
  volume={125},
  pages={207--219},
  year={2017},
  publisher={Elsevier}
}

@inproceedings{aralikatte2018fault,
  title={Fault in your stars: an analysis of Android app reviews},
  author={Aralikatte, Rahul and Sridhara, Giriprasad and Gantayat, Neelamadhav and Mani, Senthil},
  booktitle={Proceedings of the ACM India Joint International Conference on Data Science and Management of Data},
  pages={57--66},
  year={2018},
  organization={ACM}
}

@inproceedings{wang2018android,
  title={Why are Android apps removed from Google Play?: a large-scale empirical study},
  author={Wang, Haoyu and Li, Hao and Li, Li and Guo, Yao and Xu, Guoai},
  booktitle={Proceedings of the 15th International Conference on Mining Software Repositories},
  pages={231--242},
  year={2018},
  organization={ACM}
}

@Book{xie2015,
  title = {Dynamic Documents with {R} and knitr},
  author = {Yihui Xie},
  publisher = {Chapman and Hall/CRC},
  address = {Boca Raton, Florida},
  year = {2015},
  edition = {2nd},
  note = {ISBN 978-1498716963},
  url = {http://yihui.name/knitr/},
}

@article{kitchenham2004procedures,
  title={Procedures for performing systematic reviews},
  author={Kitchenham, Barbara},
  journal={Keele, UK, Keele University},
  volume={33},
  number={2004},
  pages={1--26},
  year={2004}
}

% ---- INITIAL SEED BUG PREDICTION ---- %
@article{DAmbros2010,
archivePrefix = {arXiv},
arxivId = {arXiv:1402.3873v2},
author = {D'Ambros, Marco and Lanza, Michele and Robbes, Romain},
doi = {10.1109/MSR.2010.5463279},
eprint = {arXiv:1402.3873v2},
isbn = {9781424468034},
issn = {02705257},
journal = {Proceedings - International Conference on Software Engineering},
keywords = {[Electronic Manuscript]},
pages = {31--41},
pmid = {14571374},
title = {{An extensive comparison of bug prediction approaches}},
year = {2010}
}
@inproceedings{Lewis2013,
author = {Lewis, Chris and Lin, Zhongpeng and Sadowski, Caitlin and Zhu, Xiaoyan and Ou, Rong and Whitehead, E. James},
booktitle = {2013 35th International Conference on Software Engineering (ICSE)},
doi = {10.1109/ICSE.2013.6606583},
isbn = {978-1-4673-3076-3},
month = {may},
pages = {372--381},
publisher = {IEEE},
title = {{Does bug prediction support human developers? Findings from a Google case study}},
url = {http://ieeexplore.ieee.org/document/6606583/},
year = {2013}
}
@article{Arisholm2010,
author = {Arisholm, Erik and Briand, Lionel C and Johannessen, Eivind B},
doi = {10.1016/j.jss.2009.06.055},
isbn = {0164-1212},
issn = {01641212},
journal = {Journal of Systems and Software},
keywords = {Cost-effectiveness,Fault prediction models,Verification},
number = {1},
pages = {2--17},
title = {{A systematic and comprehensive investigation of methods to build and evaluate fault prediction models}},
url = {https://ac.els-cdn.com/S0164121209001605/1-s2.0-S0164121209001605-main.pdf?{\_}tid=92a2f1a8-4bd2-4fe0-afdd-6ba58bccd31d{\&}acdnat=1536888305{\_}7d2566bc695559cbb4e74fdee3304bc0},
volume = {83},
year = {2010}
}
@article{Gyimothy2005,
author = {Gyimothy, T. and Ferenc, R. and Siket, I.},
doi = {10.1109/TSE.2005.112},
issn = {0098-5589},
journal = {IEEE Transactions on Software Engineering},
month = {oct},
number = {10},
pages = {897--910},
title = {{Empirical validation of object-oriented metrics on open source software for fault prediction}},
url = {http://ieeexplore.ieee.org/document/1542070/},
volume = {31},
year = {2005}
}
@article{Hall2012,
author = {Hall, T. and Beecham, S. and Bowes, D. and Gray, D. and Counsell, S.},
doi = {10.1109/TSE.2011.103},
issn = {0098-5589},
journal = {IEEE Transactions on Software Engineering},
month = {nov},
number = {6},
pages = {1276--1304},
title = {{A Systematic Literature Review on Fault Prediction Performance in Software Engineering}},
url = {http://ieeexplore.ieee.org/document/6035727/},
volume = {38},
year = {2012}
}
@misc{Catal2009review,
archivePrefix = {arXiv},
arxivId = {arXiv:1011.1669v3},
author = {Catal, Cagatay and Diri, Banu},
booktitle = {Expert Systems with Applications},
doi = {10.1016/j.eswa.2008.10.027},
eprint = {arXiv:1011.1669v3},
isbn = {0957-4174},
issn = {09574174},
keywords = {Automated fault prediction models,Expert systems,Machine learning,Method-level metrics,Public datasets},
number = {4},
pages = {7346--7354},
pmid = {25246403},
title = {{A systematic review of software fault prediction studies}},
url = {https://ac.els-cdn.com/S0957417408007215/1-s2.0-S0957417408007215-main.pdf?{\_}tid=f8b58ec9-c9a8-42d6-8bfd-d73c0f25d69e{\&}acdnat=1536697658{\_}4a8c6621a4a2ac4f49d65e0687927d91},
volume = {36},
year = {2009}
}

% ---- END INITIAL SEED BUG PREDICTION ---- %
% ---- BUG PREDICTION ---- %
@inproceedings{giger2012,
 author = {Giger, Emanuel and D'Ambros, Marco and Pinzger, Martin and Gall, Harald C.},
 title = {Method-level Bug Prediction},
 booktitle = {Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement},
 series = {ESEM '12},
 year = {2012},
 isbn = {978-1-4503-1056-7},
 location = {Lund, Sweden},
 pages = {171--180},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/2372251.2372285},
 doi = {10.1145/2372251.2372285},
 acmid = {2372285},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {code metrics, fine-grained source code changes, method-level bug prediction},
}
@INPROCEEDINGS{wang2016,
author={S. Wang and T. Liu and L. Tan},
booktitle={2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE)},
title={Automatically Learning Semantic Features for Defect Prediction},
year={2016},
volume={},
number={},
pages={297-308},
keywords={belief networks;neural nets;program diagnostics;programming language semantics;public domain software;source code (software);semantic feature learning;software defect prediction;representation-learning algorithm;deep learning;programs semantic representation;source code;deep belief network;token vectors;abstract syntax trees;DBN;AST;open source projects;within-project defect prediction;cross-project defect prediction;WPDP;CPDP;Semantics;Feature extraction;Training;Predictive models;Buildings;Syntactics;Data models;defect prediction;feature generation;deep learning},
doi={10.1145/2884781.2884804},
ISSN={1558-1225},
month={May},
}
@inproceedings{zimmermann2009,
 author = {Zimmermann, Thomas and Nagappan, Nachiappan and Gall, Harald and Giger, Emanuel and Murphy, Brendan},
 title = {Cross-project Defect Prediction: A Large Scale Experiment on Data vs. Domain vs. Process},
 booktitle = {Proceedings of the the 7th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering},
 series = {ESEC/FSE '09},
 year = {2009},
 isbn = {978-1-60558-001-2},
 location = {Amsterdam, The Netherlands},
 pages = {91--100},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/1595696.1595713},
 doi = {10.1145/1595696.1595713},
 acmid = {1595713},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {churn, cross-project, decision trees, defect prediction, logistic regression, prediction quality},
}
@inproceedings{hassan2009,
 author = {Hassan, Ahmed E.},
 title = {Predicting Faults Using the Complexity of Code Changes},
 booktitle = {Proceedings of the 31st International Conference on Software Engineering},
 series = {ICSE '09},
 year = {2009},
 isbn = {978-1-4244-3453-4},
 pages = {78--88},
 numpages = {11},
 url = {http://dx.doi.org/10.1109/ICSE.2009.5070510},
 doi = {10.1109/ICSE.2009.5070510},
 acmid = {1555024},
 publisher = {IEEE Computer Society},
 address = {Washington, DC, USA},
}
@inproceedings{kim2007,
 author = {Kim, Sunghun and Zimmermann, Thomas and Whitehead Jr., E. James and Zeller, Andreas},
 title = {Predicting Faults from Cached History},
 booktitle = {Proceedings of the 29th International Conference on Software Engineering},
 series = {ICSE '07},
 year = {2007},
 isbn = {0-7695-2828-7},
 pages = {489--498},
 numpages = {10},
 url = {http://dx.doi.org/10.1109/ICSE.2007.66},
 doi = {10.1109/ICSE.2007.66},
 acmid = {1248881},
 publisher = {IEEE Computer Society},
 address = {Washington, DC, USA},
}
@inproceedings{rahman2011,
 author = {Rahman, Foyzur and Posnett, Daryl and Hindle, Abram and Barr, Earl and Devanbu, Premkumar},
 title = {BugCache for Inspections: Hit or Miss?},
 booktitle = {Proceedings of the 19th ACM SIGSOFT Symposium and the 13th European Conference on Foundations of Software Engineering},
 series = {ESEC/FSE '11},
 year = {2011},
 isbn = {978-1-4503-0443-6},
 location = {Szeged, Hungary},
 pages = {322--331},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/2025113.2025157},
 doi = {10.1145/2025113.2025157},
 acmid = {2025157},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {empirical software engineering, fault prediction, inspection},
}
@INPROCEEDINGS{Rahman2013,
author={F. Rahman and P. Devanbu},
booktitle={2013 35th International Conference on Software Engineering (ICSE)},
title={How, and why, process metrics are better},
year={2013},
volume={},
number={},
pages={432-441},
keywords={software metrics;software performance evaluation;software quality;statistical analysis;process metrics;defect prediction;quality-assurance efforts;defect-prone files;statistical tools;software metrics;model deployment;code metrics;performance;stability;portability;Measurement;Predictive models;Object oriented modeling;Training;Support vector machines;Software;Complexity theory},
doi={10.1109/ICSE.2013.6606589},
ISSN={0270-5257},
month={May},}
@article{DiNucci2018,
author={Di Nucci,D. and Palomba,F. and De Rosa,G. and Bavota,G. and Oliveto,R. and De Lucia,A.},
year={2018},
title={A Developer Centered Bug Prediction Model},
journal={IEEE Transactions on Software Engineering},
volume={44},
number={1},
pages={5-24},
language={English},
url={www.scopus.com}
}
@article{DiNucci2018,
author={Di Nucci,D. and Palomba,F. and De Rosa,G. and Bavota,G. and Oliveto,R. and De Lucia,A.},
year={2018},
title={A Developer Centered Bug Prediction Model},
journal={IEEE Transactions on Software Engineering},
volume={44},
number={1},
pages={5-24},
language={English},
url={www.scopus.com}
}
@article{DAmbros2012,
author={D'Ambros,M. and Lanza,M. and Robbes,R.},
year={2012},
title={Evaluating defect prediction approaches: A benchmark and an extensive comparison},
journal={Empirical Software Engineering},
volume={17},
number={4-5},
pages={531-577},
note={Cited By :167},
language={English},
url={www.scopus.com},
}
@article{Catal2011,
author={Catal,C.},
year={2011},
title={Software fault prediction: A literature review and current trends},
journal={Expert Systems with Applications},
volume={38},
number={4},
pages={4626-4636},
note={Cited By :138},
language={English},
url={www.scopus.com},
}
@article{Catal2009investigating,
author={Catal,C. and Diri,B.},
year={2009},
title={Investigating the effect of dataset size, metrics sets, and feature selection techniques on software fault prediction problem},
journal={Information Sciences},
volume={179},
number={8},
pages={1040-1058},
note={Cited By :109},
language={English},
url={www.scopus.com},
}
@article{Lessman2008,
author={Lessmann,S. and Baesens,B. and Mues,C. and Pietsch,S.},
year={2008},
title={Benchmarking classification models for software defect prediction: A proposed framework and novel findings},
journal={IEEE Transactions on Software Engineering},
volume={34},
number={4},
pages={485-496},
note={Cited By :491},
language={English},
url={www.scopus.com},
}
@inproceedings{Herzig2013,
author={Herzig,K. and Just,S. and Zeller,A.},
editor={ },
year={2013},
title={It's not a bug, it's a feature: How misclassification impacts bug prediction},
booktitle={Proceedings - International Conference on Software Engineering},
pages={392-401},
note={Cited By :128},
language={English},
url={www.scopus.com},
}
@article{Gao2011,
author={Gao,K. and Khoshgoftaar,T. M. and Wang,H. and Seliya,N.},
year={2011},
title={Choosing software metrics for defect prediction: An investigation on feature selection techniques},
journal={Software - Practice and Experience},
volume={41},
number={5},
pages={579-606},
note={Cited By :107},
language={English},
url={www.scopus.com},
}
@inproceedings{Kamei2010,
 author = {Kamei, Yasutaka and Matsumoto, Shinsuke and Monden, Akito and Matsumoto, Ken-ichi and Adams, Bram and Hassan, Ahmed E.},
 title = {Revisiting Common Bug Prediction Findings Using Effort-aware Models},
 booktitle = {Proceedings of the 2010 IEEE International Conference on Software Maintenance},
 series = {ICSM '10},
 year = {2010},
 isbn = {978-1-4244-8630-4},
 pages = {1--10},
 numpages = {10},
 url = {http://dx.doi.org/10.1109/ICSM.2010.5609530},
 doi = {10.1109/ICSM.2010.5609530},
 acmid = {1913298},
 publisher = {IEEE Computer Society},
 address = {Washington, DC, USA},
}
@inproceedings{Lamkanfi2011,
 author = {Lamkanfi, Ahmed and Demeyer, Serge and Soetens, Quinten David and Verdonck, Tim},
 title = {Comparing Mining Algorithms for Predicting the Severity of a Reported Bug},
 booktitle = {Proceedings of the 2011 15th European Conference on Software Maintenance and Reengineering},
 series = {CSMR '11},
 year = {2011},
 isbn = {978-0-7695-4343-7},
 pages = {249--258},
 numpages = {10},
 url = {http://dx.doi.org/10.1109/CSMR.2011.31},
 doi = {10.1109/CSMR.2011.31},
 acmid = {1962803},
 publisher = {IEEE Computer Society},
 address = {Washington, DC, USA},
 keywords = {Text Mining, Naive Bayes, Bug Reports, Bug Severity, Bugzilla},
}
@article{Radjenovic2013,
 author = {Radjenovi\'{c}, Danijel and Heri\v{c}ko, Marjan and Torkar, Richard and \v{Z}ivkovi\v{c}, Ale\v{s}},
 title = {Software Fault Prediction Metrics},
 journal = {Information and Software Technology},
 issue_date = {August 2013},
 volume = {55},
 number = {8},
 month = aug,
 year = {2013},
 issn = {0950-5849},
 pages = {1397--1418},
 numpages = {22},
 url = {http://dx.doi.org/10.1016/j.infsof.2013.02.009},
 doi = {10.1016/j.infsof.2013.02.009},
 acmid = {2771005},
 publisher = {Butterworth-Heinemann},
 address = {Newton, MA, USA},
 keywords = {Software fault prediction, Software metric, Systematic literature review},
}
@article{Malhotra2015,
 author = {Malhotra, Ruchika},
 title = {A Systematic Review of Machine Learning Techniques for Software Fault Prediction},
 journal = {Applied Soft Computing},
 issue_date = {February 2015},
 volume = {27},
 number = {C},
 month = feb,
 year = {2015},
 issn = {1568-4946},
 pages = {504--518},
 numpages = {15},
 url = {http://dx.doi.org/10.1016/j.asoc.2014.11.023},
 doi = {10.1016/j.asoc.2014.11.023},
 acmid = {2803085},
 publisher = {Elsevier Science Publishers B. V.},
 address = {Amsterdam, The Netherlands, The Netherlands},
 keywords = {Machine learning, Software fault proneness, Systematic literature review},
}
@inproceedings{Giger2011,
 author = {Giger, Emanuel and Pinzger, Martin and Gall, Harald C.},
 title = {Comparing Fine-grained Source Code Changes and Code Churn for Bug Prediction},
 booktitle = {Proceedings of the 8th Working Conference on Mining Software Repositories},
 series = {MSR '11},
 year = {2011},
 isbn = {978-1-4503-0574-7},
 location = {Waikiki, Honolulu, HI, USA},
 pages = {83--92},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/1985441.1985456},
 doi = {10.1145/1985441.1985456},
 acmid = {1985456},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {code churn, nonlinear regression, prediction models, software bugs, source code changes},
}
@inproceedings{Kim2011,
 author = {Kim, Sunghun and Zhang, Hongyu and Wu, Rongxin and Gong, Liang},
 title = {Dealing with Noise in Defect Prediction},
 booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
 series = {ICSE '11},
 year = {2011},
 isbn = {978-1-4503-0445-0},
 location = {Waikiki, Honolulu, HI, USA},
 pages = {481--490},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/1985793.1985859},
 doi = {10.1145/1985793.1985859},
 acmid = {1985859},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {buggy changes, buggy files, data quality, defect prediction, noise resistance},
}
@article{Jiang2008,
 author = {Jiang, Yue and Cukic, Bojan and Ma, Yan},
 title = {Techniques for Evaluating Fault Prediction Models},
 journal = {Empirical Software Engineering},
 issue_date = {October   2008},
 volume = {13},
 number = {5},
 month = oct,
 year = {2008},
 issn = {1382-3256},
 pages = {561--595},
 numpages = {35},
 url = {http://dx.doi.org/10.1007/s10664-008-9079-3},
 doi = {10.1007/s10664-008-9079-3},
 acmid = {1416836},
 publisher = {Kluwer Academic Publishers},
 address = {Hingham, MA, USA},
 keywords = {Empirical studies, Fault-prediction models, Model evaluation, Predictive models in software engineering},
}
@Article{Bowes2018,
author="Bowes, David
and Hall, Tracy
and Petri{\'{c}}, Jean",
title="Software defect prediction: do different classifiers find the same defects?",
journal="Software Quality Journal",
year="2018",
month="Jun",
day="01",
volume="26",
number="2",
pages="525--552",
issn="1573-1367",
doi="10.1007/s11219-016-9353-3",
url="https://doi.org/10.1007/s11219-016-9353-3"
}
@inproceedings{wWng2011,
  title={How many software metrics should be selected for defect prediction?},
  author={Wang, Huanjing and Khoshgoftaar, Taghi M and Seliya, Naeem},
  booktitle={FLAIRS Conference},
  year={2011}
}
@inproceedings{Jiang2013,
 author = {Jiang, Tian and Tan, Lin and Kim, Sunghun},
 title = {Personalized Defect Prediction},
 booktitle = {Proceedings of the 28th IEEE/ACM International Conference on Automated Software Engineering},
 series = {ASE'13},
 year = {2013},
 isbn = {978-1-4799-0215-6},
 location = {Silicon Valley, CA, USA},
 pages = {279--289},
 numpages = {11},
 url = {https://doi.org/10.1109/ASE.2013.6693087},
 doi = {10.1109/ASE.2013.6693087},
 acmid = {3107693},
 publisher = {IEEE Press},
 address = {Piscataway, NJ, USA},
 keywords = {change classification, machine learning, personalized defect prediction, software reliability},
}
@inproceedings{Ghotra2015,
 author = {Ghotra, Baljinder and McIntosh, Shane and Hassan, Ahmed E.},
 title = {Revisiting the Impact of Classification Techniques on the Performance of Defect Prediction Models},
 booktitle = {Proceedings of the 37th International Conference on Software Engineering - Volume 1},
 series = {ICSE '15},
 year = {2015},
 isbn = {978-1-4799-1934-5},
 location = {Florence, Italy},
 pages = {789--800},
 numpages = {12},
 url = {http://dl.acm.org/citation.cfm?id=2818754.2818850},
 acmid = {2818850},
 publisher = {IEEE Press},
 address = {Piscataway, NJ, USA},
}
@inproceedings{Lee2011,
 author = {Lee, Taek and Nam, Jaechang and Han, DongGyun and Kim, Sunghun and In, Hoh Peter},
 title = {Micro Interaction Metrics for Defect Prediction},
 booktitle = {Proceedings of the 19th ACM SIGSOFT Symposium and the 13th European Conference on Foundations of Software Engineering},
 series = {ESEC/FSE '11},
 year = {2011},
 isbn = {978-1-4503-0443-6},
 location = {Szeged, Hungary},
 pages = {311--321},
 numpages = {11},
 url = {http://doi.acm.org/10.1145/2025113.2025156},
 doi = {10.1145/2025113.2025156},
 acmid = {2025156},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {defect prediction, micro interaction metrics, mylyn},
}
@inproceedings{Matsumoto2010,
 author = {Matsumoto, Shinsuke and Kamei, Yasutaka and Monden, Akito and Matsumoto, Ken-ichi and Nakamura, Masahide},
 title = {An Analysis of Developer Metrics for Fault Prediction},
 booktitle = {Proceedings of the 6th International Conference on Predictive Models in Software Engineering},
 series = {PROMISE '10},
 year = {2010},
 isbn = {978-1-4503-0404-7},
 location = {Timi\şoara, Romania},
 pages = {18:1--18:9},
 articleno = {18},
 numpages = {9},
 url = {http://doi.acm.org/10.1145/1868328.1868356},
 doi = {10.1145/1868328.1868356},
 acmid = {1868356},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {developer metrics, fault prediction, human factor},
}
@ARTICLE{Shepperd2014,
author={M. Shepperd and D. Bowes and T. Hall},
journal={IEEE Transactions on Software Engineering},
title={Researcher Bias: The Use of Machine Learning in Software Defect Prediction},
year={2014},
volume={40},
number={6},
pages={603-616},
keywords={learning (artificial intelligence);object-oriented programming;reverse engineering;software metrics;software performance evaluation;statistical analysis;machine learning;software defect prediction;defect-prone software component prediction;performance evaluation;reverse engineering;common response variable;random effects ANOVA model;model building factors;classifier factor;data set factor;input metrics factor;researcher group factor;researcher bias;blind analysis;reporting protocol improvement;intergroup studies;Software;Predictive models;Correlation;Data models;Buildings;Software engineering;Measurement;Software defect prediction;meta-analysis;researcher bias},
doi={10.1109/TSE.2014.2322358},
ISSN={0098-5589},
month={June}
}
@inproceedings{khoshgoftaar2010,
  title={Attribute selection and imbalanced data: Problems in software defect prediction},
  author={Khoshgoftaar, Taghi M and Gao, Kehan and Seliya, Naeem},
  booktitle={Tools with Artificial Intelligence (ICTAI), 2010 22nd IEEE International Conference on},
  volume={1},
  pages={137--144},
  year={2010},
  organization={IEEE}
}
@inproceedings{Moser2008,
 author = {Moser, Raimund and Pedrycz, Witold and Succi, Giancarlo},
 title = {A Comparative Analysis of the Efficiency of Change Metrics and Static Code Attributes for Defect Prediction},
 booktitle = {Proceedings of the 30th International Conference on Software Engineering},
 series = {ICSE '08},
 year = {2008},
 isbn = {978-1-60558-079-1},
 location = {Leipzig, Germany},
 pages = {181--190},
 numpages = {10},
 url = {http://doi.acm.org/10.1145/1368088.1368114},
 doi = {10.1145/1368088.1368114},
 acmid = {1368114},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {cost-sensitive classification, defect prediction, software metrics},
}
@ARTICLE{Song2011,
author={Q. Song and Z. Jia and M. Shepperd and S. Ying and J. Liu},
journal={IEEE Transactions on Software Engineering},
title={A General Software Defect-Proneness Prediction Framework},
year={2011},
volume={37},
number={3},
pages={356-370},
keywords={learning (artificial intelligence);software fault tolerance;software performance evaluation;software defect proneness prediction framework;scheme evaluation;competing learning schemes;defect predictor;Software;Training data;Predictive models;Buildings;Data models;Prediction algorithms;Training;Software defect prediction;software defect-proneness prediction;machine learning;scheme evaluation.},
doi={10.1109/TSE.2010.90},
ISSN={0098-5589},
month={May},}
% ---- END BUG PREDICTION ---- %

%% Software Ecosystems References
@inproceedings{Abdalkareem2017,
  doi = {10.1145/3106237.3106267},
  url = {https://doi.org/10.1145/3106237.3106267},
  year  = {2017},
  publisher = {{ACM} Press},
  author = {Rabe Abdalkareem and Olivier Nourry and Sultan Wehaibi and Suhaib Mujahid and Emad Shihab},
  title = {Why do developers use trivial packages? an empirical case study on npm},
  booktitle = {Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering  - {ESEC}/{FSE} 2017}
}

@inproceedings{Abate2009,
  doi = {10.1109/esem.2009.5316017},
  url = {https://doi.org/10.1109/esem.2009.5316017},
  year  = {2009},
  month = {oct},
  publisher = {{IEEE}},
  author = {Pietro Abate and Roberto Di Cosmo and Jaap Boender and Stefano Zacchiroli},
  title = {Strong dependencies between software components},
  booktitle = {2009 3rd International Symposium on Empirical Software Engineering and Measurement}
}

@inproceedings{Abate2011,
  doi = {10.1109/icdew.2011.5767626},
  url = {https://doi.org/10.1109/icdew.2011.5767626},
  year  = {2011},
  month = {apr},
  publisher = {{IEEE}},
  author = {Pietro Abate and Roberto Di Cosmo},
  title = {Predicting upgrade failures using dependency analysis},
  booktitle = {2011 {IEEE} 27th International Conference on Data Engineering Workshops}
}

@article{Bavota2014,
  doi = {10.1007/s10664-014-9325-9},
  url = {https://doi.org/10.1007/s10664-014-9325-9},
  year  = {2014},
  month = {sep},
  publisher = {Springer Nature},
  volume = {20},
  number = {5},
  pages = {1275--1317},
  author = {Gabriele Bavota and Gerardo Canfora and Massimiliano Di Penta and Rocco Oliveto and Sebastiano Panichella},
  title = {How the Apache community upgrades dependencies: an evolutionary study},
  journal = {Empirical Software Engineering}
}

@inproceedings{Blincoe2015,
  doi = {10.1109/msr.2015.26},
  url = {https://doi.org/10.1109/msr.2015.26},
  year  = {2015},
  month = {may},
  publisher = {{IEEE}},
  author = {Kelly Blincoe and Francis Harrison and Daniela Damian},
  title = {Ecosystems in {GitHub} and a Method for Ecosystem Identification Using Reference Coupling},
  booktitle = {2015 {IEEE}/{ACM} 12th Working Conference on Mining Software Repositories}
}

@inproceedings{Bogart2016,
  doi = {10.1145/2950290.2950325},
  url = {https://doi.org/10.1145/2950290.2950325},
  year  = {2016},
  publisher = {{ACM} Press},
  author = {Christopher Bogart and Christian K\"{a}stner and James Herbsleb and Ferdian Thung},
  title = {How to break an {API}: cost negotiation and community values in three software ecosystems},
  booktitle = {Proceedings of the 2016 24th {ACM} {SIGSOFT} International Symposium on Foundations of Software Engineering - {FSE} 2016}
}

@inproceedings{Claes2015,
  doi = {10.1109/msr.2015.27},
  url = {https://doi.org/10.1109/msr.2015.27},
  year  = {2015},
  month = {may},
  publisher = {{IEEE}},
  author = {Maelick Claes and Tom Mens and Roberto Di Cosmo and Jerome Vouillon},
  title = {A Historical Analysis of Debian Package Incompatibilities},
  booktitle = {2015 {IEEE}/{ACM} 12th Working Conference on Mining Software Repositories}
}

@article{Constantinou2017,
  doi = {10.1007/s11334-017-0303-4},
  url = {https://doi.org/10.1007/s11334-017-0303-4},
  year  = {2017},
  month = {aug},
  publisher = {Springer Nature},
  volume = {13},
  number = {2-3},
  pages = {101--115},
  author = {Eleni Constantinou and Tom Mens},
  title = {An empirical comparison of developer retention in the {RubyGems} and npm software ecosystems},
  journal = {Innovations in Systems and Software Engineering}
}

@inproceedings{Cox2015,
  doi = {10.1109/icse.2015.140},
  url = {https://doi.org/10.1109/icse.2015.140},
  year  = {2015},
  month = {may},
  publisher = {{IEEE}},
  author = {Joel Cox and Eric Bouwers and Marko van Eekelen and Joost Visser},
  title = {Measuring Dependency Freshness in Software Systems},
  booktitle = {2015 {IEEE}/{ACM} 37th {IEEE} International Conference on Software Engineering}
}

@inproceedings{Decan2017,
  doi = {10.1109/saner.2017.7884604},
  url = {https://doi.org/10.1109/saner.2017.7884604},
  year  = {2017},
  month = {feb},
  publisher = {{IEEE}},
  author = {Alexandre Decan and Tom Mens and Maelick Claes},
  title = {An empirical comparison of dependency issues in {OSS} packaging ecosystems},
  booktitle = {2017 {IEEE} 24th International Conference on Software Analysis,  Evolution and Reengineering ({SANER})}
}

@article{Decan2018,
  doi = {10.1007/s10664-017-9589-y},
  url = {https://doi.org/10.1007/s10664-017-9589-y},
  year  = {2018},
  month = {feb},
  publisher = {Springer Nature},
  author = {Alexandre Decan and Tom Mens and Philippe Grosjean},
  title = {An empirical comparison of dependency network evolution in seven software packaging ecosystems},
  journal = {Empirical Software Engineering}
}

@inproceedings{Dietrich2014,
  doi = {10.1109/csmr-wcre.2014.6747226},
  url = {https://doi.org/10.1109/csmr-wcre.2014.6747226},
  year  = {2014},
  month = {feb},
  publisher = {{IEEE}},
  author = {Jens Dietrich and Kamil Jezek and Premek Brada},
  title = {Broken promises: An empirical study into evolution problems in Java programs caused by library upgrades},
  booktitle = {2014 Software Evolution Week - {IEEE} Conference on Software Maintenance,  Reengineering,  and Reverse Engineering ({CSMR}-{WCRE})}
}

@article{Dittrich2014,
  doi = {10.1016/j.infsof.2014.02.012},
  url = {https://doi.org/10.1016/j.infsof.2014.02.012},
  year  = {2014},
  month = {nov},
  publisher = {Elsevier {BV}},
  volume = {56},
  number = {11},
  pages = {1436--1456},
  author = {Yvonne Dittrich},
  title = {Software engineering beyond the project {\textendash} Sustaining software ecosystems},
  journal = {Information and Software Technology}
}

@inproceedings{Hejderup2018,
  doi = {10.1145/3183399.3183417},
  url = {https://doi.org/10.1145/3183399.3183417},
  year  = {2018},
  publisher = {{ACM} Press},
  author = {Joseph Hejderup and Arie van Deursen and Georgios Gousios},
  title = {Software ecosystem call graph for dependency management},
  booktitle = {Proceedings of the 40th International Conference on Software Engineering New Ideas and Emerging Results - {ICSE}-{NIER} {\textquotesingle}18}
}

@article{Hora2016,
  doi = {10.1007/s11219-016-9344-4},
  url = {https://doi.org/10.1007/s11219-016-9344-4},
  year  = {2016},
  month = {oct},
  publisher = {Springer Nature},
  volume = {26},
  number = {1},
  pages = {161--191},
  author = {Andr{\'{e}} Hora and Romain Robbes and Marco Tulio Valente and Nicolas Anquetil and Anne Etien and St{\'{e}}phane Ducasse},
  title = {How do developers react to {API} evolution? A large-scale empirical study},
  journal = {Software Quality Journal}
}

@article{Izquierdo2018,
  doi = {10.1109/ms.2018.290101357},
  url = {https://doi.org/10.1109/ms.2018.290101357},
  year  = {2018},
  publisher = {Institute of Electrical and Electronics Engineers ({IEEE})},
  pages = {1--1},
  author = {Daniel Izquierdo and Jesus Gonzalez-Barahona and Lars Kurth and Gregorio Robles},
  title = {Software Development Analytics for Xen: Why and How},
  journal = {{IEEE} Software}
}

@article{Jansen2014,
  doi = {10.1016/j.infsof.2014.04.006},
  url = {https://doi.org/10.1016/j.infsof.2014.04.006},
  year  = {2014},
  month = {nov},
  publisher = {Elsevier {BV}},
  volume = {56},
  number = {11},
  pages = {1508--1519},
  author = {Slinger Jansen},
  title = {Measuring the health of open source software ecosystems: Beyond the scope of project health},
  journal = {Information and Software Technology}
}

@inproceedings{Kikas2017,
  doi = {10.1109/msr.2017.55},
  url = {https://doi.org/10.1109/msr.2017.55},
  year  = {2017},
  month = {may},
  publisher = {{IEEE}},
  author = {Riivo Kikas and Georgios Gousios and Marlon Dumas and Dietmar Pfahl},
  title = {Structure and Evolution of Package Dependency Networks},
  booktitle = {2017 {IEEE}/{ACM} 14th International Conference on Mining Software Repositories ({MSR})}
}

@article{Kitchenham2004,
  year = {2004},
  author = {Barbara Kitchenham},
  title = {Procedures for Performing Systematic Reviews},
  volume = {33},
  number = {1},
  pages = {1--26},
  journal = {Keele},
  publisher = {UK, Keele University}
}

@article{Kula2017,
  doi = {10.1007/s10664-017-9521-5},
  url = {https://doi.org/10.1007/s10664-017-9521-5},
  year  = {2017},
  month = {may},
  publisher = {Springer Nature},
  volume = {23},
  number = {1},
  pages = {384--417},
  author = {Raula Gaikovina Kula and Daniel M. German and Ali Ouni and Takashi Ishio and Katsuro Inoue},
  title = {Do developers update their library dependencies?},
  journal = {Empirical Software Engineering}
}

@inproceedings{Kula2017-2,
  doi = {10.1109/saner.2017.7884643},
  url = {https://doi.org/10.1109/saner.2017.7884643},
  year  = {2017},
  month = {feb},
  publisher = {{IEEE}},
  author = {Raula Gaikovina Kula and Daniel M. German and Takashi Ishio and Ali Ouni and Katsuro Inoue},
  title = {An exploratory study on library aging by monitoring client usage in a software ecosystem},
  booktitle = {2017 {IEEE} 24th International Conference on Software Analysis,  Evolution and Reengineering ({SANER})}
}

@online{Linux2016,
  author = {Paul Brown},
  title = {State of the Union: npm},
  year = {2016},
  url = {https://www.linux.com/news/event/Nodejs/2016/state-union-npm},
  urldate = {2018-10-11}
}

@phdthesis{Lungu2009,
  author       = {Mircea Lungu},
  title        = {Reverse Engineering Software Ecosystems},
  school       = {University of Lugano},
  year         = 2009
}

@inproceedings{Malloy2017,
  doi = {10.1109/esem.2017.45},
  url = {https://doi.org/10.1109/esem.2017.45},
  year  = {2017},
  month = {nov},
  publisher = {{IEEE}},
  author = {Brian A. Malloy and James F. Power},
  title = {Quantifying the Transition from Python 2 to 3: An Empirical Study of Python Applications},
  booktitle = {2017 {ACM}/{IEEE} International Symposium on Empirical Software Engineering and Measurement ({ESEM})}
}

@article{Malloy2018,
  doi = {10.1007/s10664-018-9637-2},
  url = {https://doi.org/10.1007/s10664-018-9637-2},
  year  = {2018},
  month = {jul},
  publisher = {Springer Nature},
  author = {Brian A. Malloy and James F. Power},
  title = {An empirical analysis of the transition from Python 2 to Python 3},
  journal = {Empirical Software Engineering}
}

@article{Manikas2016,
  doi = {10.1016/j.jss.2016.02.003},
  url = {https://doi.org/10.1016/j.jss.2016.02.003},
  year  = {2016},
  month = {jul},
  publisher = {Elsevier {BV}},
  volume = {117},
  pages = {84--103},
  author = {Konstantinos Manikas},
  title = {Revisiting software ecosystems Research: A longitudinal literature study},
  journal = {Journal of Systems and Software}
}

@inproceedings{McDonnell2013,
  doi = {10.1109/icsm.2013.18},
  url = {https://doi.org/10.1109/icsm.2013.18},
  year  = {2013},
  month = {sep},
  publisher = {{IEEE}},
  author = {Tyler McDonnell and Baishakhi Ray and Miryung Kim},
  title = {An Empirical Study of {API} Stability and Adoption in the Android Ecosystem},
  booktitle = {2013 {IEEE} International Conference on Software Maintenance}
}

@incollection{Mens2013,
  doi = {10.1007/978-3-642-45398-4_10},
  url = {https://doi.org/10.1007/978-3-642-45398-4_10},
  year  = {2013},
  month = {dec},
  publisher = {Springer Berlin Heidelberg},
  pages = {297--326},
  author = {Tom Mens and Ma{\'{a}}lick Claes and Philippe Grosjean and Alexander Serebrenik},
  title = {Studying Evolving Software Ecosystems based on Ecological Models},
  booktitle = {Evolving Software Systems}
}

@book{Messerschmitt2003,
  Author = {David G. Messerschmitt and Clemens Szyperski},
  Title = {Software Ecosystem: Understanding an Indispensable Technology and Industry (MIT Press)},
  Publisher = {The MIT Press},
  Year = {2003},
  ISBN = {0262134322},
}

@online{NPM2016,
  author = {I. Z. Schlueter},
  title = {The npm Blog: kik, left-pad and npm},
  year = {2016},
  url = {https://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm},
  urldate = {2018-10-15}
}

@article{Raemaekers2017,
  doi = {10.1016/j.jss.2016.04.008},
  url = {https://doi.org/10.1016/j.jss.2016.04.008},
  year  = {2017},
  month = {jul},
  publisher = {Elsevier {BV}},
  volume = {129},
  pages = {140--158},
  author = {S. Raemaekers and A. van Deursen and J. Visser},
  title = {Semantic versioning and impact of breaking changes in the Maven repository},
  journal = {Journal of Systems and Software}
}

@inproceedings{Rajlich2014,
  doi = {10.1145/2593882.2593893},
  url = {https://doi.org/10.1145/2593882.2593893},
  year  = {2014},
  publisher = {{ACM} Press},
  author = {V{\'{a}}clav Rajlich},
  title = {Software evolution and maintenance},
  booktitle = {Proceedings of the on Future of Software Engineering - {FOSE} 2014}
}

@online{RedMonk2018,
  author = {Stephen O'Grady},
  title = {The RedMonk Programming Language Rankings: January 2018},
  year = {2018},
  url = {https://redmonk.com/sogrady/2018/03/07/language-rankings-1-18/},
  urldate = {2018-10-11}
}

@inproceedings{Robbes2012,
  doi = {10.1145/2393596.2393662},
  url = {https://doi.org/10.1145/2393596.2393662},
  year  = {2012},
  publisher = {{ACM} Press},
  author = {Romain Robbes and Mircea Lungu and David R\"{o}thlisberger},
  title = {How do developers react to {API} deprecation?},
  booktitle = {Proceedings of the {ACM} {SIGSOFT} 20th International Symposium on the Foundations of Software Engineering - {FSE} {\textquotesingle}12}
}

@book{Stallman2002,
  title={Free software, free society: Selected essays of Richard M. Stallman},
  author={Richard Stallman},
  year={2002},
  publisher={Lulu. com},
  chapter={17},
  pages={95--95}
}

@inproceedings{Trockman2018,
  doi = {10.1145/3183440.3190335},
  url = {https://doi.org/10.1145/3183440.3190335},
  year  = {2018},
  publisher = {{ACM} Press},
  author = {Asher Trockman},
  title = {Adding sparkle to social coding},
  booktitle = {Proceedings of the 40th International Conference on Software Engineering Companion Proceeedings - {ICSE} {\textquotesingle}18}
}

@article{Teixeira2015,
  doi = {10.1186/s13174-015-0028-2},
  url = {https://doi.org/10.1186/s13174-015-0028-2},
  year  = {2015},
  month = {jul},
  publisher = {Springer Nature},
  volume = {6},
  number = {1},
  author = {Jose Teixeira and Gregorio Robles and Jes{\'{u}}s M. Gonz{\'{a}}lez-Barahona},
  title = {Lessons learned from applying social network analysis on an industrial Free/Libre/Open Source Software ecosystem},
  journal = {Journal of Internet Services and Applications}
}

%% /Software Ecosystems References
@inproceedings{LBB2013,
 author = {Linares-V\'{a}squez, Mario and Bavota, Gabriele and Bernal-C\'{a}rdenas, Carlos and Di Penta, Massimiliano and Oliveto, Rocco and Poshyvanyk, Denys},
 title = {API Change and Fault Proneness: A Threat to the Success of Android Apps},
 booktitle = {Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering},
 series = {ESEC/FSE 2013},
 year = {2013},
 isbn = {978-1-4503-2237-9},
 location = {Saint Petersburg, Russia},
 pages = {477--487},
 numpages = {11},
 url = {http://doi.acm.org/10.1145/2491411.2491428},
 doi = {10.1145/2491411.2491428},
 acmid = {2491428},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {API changes, Android, Empirical Studies, Mining Software Repositories},
}

@ARTICLE{BLB2015,
author={G. Bavota and M. Linares-Vásquez and C. E. Bernal-Cárdenas and M. D. Penta and R. Oliveto and D. Poshyvanyk},
journal={IEEE Transactions on Software Engineering},
title={The Impact of API Change- and Fault-Proneness on the User Ratings of Android Apps},
year={2015},
volume={41},
number={4},
pages={384-407},
keywords={application program interfaces;data mining;mobile computing;program debugging;software fault tolerance;system recovery;API change-proneness;API fault-proneness;user ratings;Android Apps;mobile Apps market;information technology;software repository mining;Androids;Humanoid robots;Software;History;Computer bugs;Educational institutions;Electronic mail;Mining software repositories;empirical studies;android;API changes;Mining software repositories;empirical studies;android;API changes},
doi={10.1109/TSE.2014.2367027},
ISSN={0098-5589},
month={April},}

@INPROCEEDINGS{PSG2015,
author={S. Panichella and A. Di Sorbo and E. Guzman and C. A. Visaggio and G. Canfora and H. C. Gall},
booktitle={2015 IEEE International Conference on Software Maintenance and Evolution (ICSME)},
title={How can i improve my app? Classifying user reviews for software maintenance and evolution},
year={2015},
volume={},
number={},
pages={281-290},
keywords={natural language processing;pattern classification;software maintenance;text analysis;user review classification;software maintenance;software evolution;app stores;review comments;star ratings;user feedback identification;app review classification;natural language processing;text analysis;sentiment analysis;Taxonomy;Software maintenance;Feature extraction;Natural language processing;Mobile communication;Maintenance engineering;Text analysis;User Reviews;Mobile Applications;Natural Language Processing;Sentiment Analysis;Text classification},
doi={10.1109/ICSM.2015.7332474},
ISSN={},
month={Sept},}

% START Release Engineering

@article{cesar2017a,
  title = {Frequent Releases in Open Source Software: A Systematic Review},
  author = {Cesar Brand{\~a}o Gomes da Silva, Antonio and de Figueiredo Carneiro, Glauco and Brito e Abreu, Fernando and Pessoa Monteiro, Miguel},
  year = {2017},
  key = {cesar2017frequent},
  publisher = {Multidisciplinary Digital Publishing Institute},
  pages = {109},
  journal = {Information},
  number = {3},
  volume = {8}
}
@article{rodriguez2017a,
  title = {Continuous deployment of software intensive products and services: A systematic mapping study},
  author = {Rodr{\'\i}guez, Pilar and Haghighatkhah, Alireza and Lwakatare, Lucy Ellen and Teppola, Susanna and Suomalainen, Tanja and Eskeli, Juho and Karvonen, Teemu and Kuvaja, Pasi and Verner, June M and Oivo, Markku},
  year = {2017},
  key = {rodriguez2017continuous},
  publisher = {Elsevier},
  pages = {263--291},
  journal = {Journal of Systems and Software},
  volume = {123}
}
@inproceedings{dyck2015a,
  title = {Towards definitions for release engineering and devops},
  author = {Dyck, Andrej and Penners, Ralf and Lichter, Horst},
  year = {2015},
  url = {https://www2.swc.rwth-aachen.de/docs/RELENG2015/DevOpsVsRelEng.pdf},
  key = {dyck2015towards},
  booktitle = {Release Engineering (RELENG), 2015 IEEE/ACM 3rd International Workshop on},
  organization = {IEEE},
  pages = {3--3}
}
@article{spinellis2018a,
  title = {The Challenges and Practices of Release Engineering},
  author = {Spinellis, Diomidis},
  year = {2018},
  key = {spinellis2018challenges},
  publisher = {IEEE},
  pages = {4--7},
  journal = {IEEE Software},
  number = {2},
  volume = {35}
}
@article{chen2015a,
  title = {Continuous delivery: Huge benefits, but challenges too},
  author = {Chen, Lianping},
  year = {2015},
  key = {chen2015continuous},
  publisher = {IEEE},
  pages = {50--54},
  journal = {IEEE Software},
  number = {2},
  volume = {32}
}
@inproceedings{adams2015a,
  title = {3rd International Workshop on Release Engineering (RELENG 2015)},
  author = {Adams, B. and Bellomo, S. and Bird, C. and Khomh, F. and Moir, K.},
  year = {2015},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84951851911&doi=10.1109%2fICSE.2015.321&partnerID=40&md5=4b9e0d9d5346e0b8926c9e2d34a7170d},
  abstract = {Release engineering deals with all activities inbetween regular development and actual usage of asoftware product by the end user, i.e., integration, build, testexecution, packaging and delivery of software. Although re-search on this topic goes back for decades, the increasing heterogeneity and variability of software products along withthe recent trend to reduce the release cycle to days or even hoursstarts to question some of the common beliefs and practicesof the field. For example, a project like Mozilla Firefox releasesevery 6 weeks, generating updates for dozens of existing Fire-fox versions on 5 desktop, 2 mobile and 3 mobile desktopplatforms, each of which for more than 80 locales. In this con-text, the International Workshop on Release Engineering(RELENG) aims to provide a highly interactive forum for re-searchers and practitioners to address the challenges of, findsolutions for and share experiences with release engineering, and to build connections between the various communities. © 2015 IEEE.},
  key = {Adams2015995},
  pages = {995-996},
  journal = {Proceedings - International Conference on Software Engineering},
  volume = {2},
  note = {cited By 0}
}
@article{adams2018a,
  title = {Release engineering 3.0},
  author = {Adams, B. and Bellomo, S. and Bird, C. and Debic, B. and Khomh, F. and Moir, K. and Oduinn, J.},
  year = {2018},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85043684495&doi=10.1109%2fMS.2018.1661327&partnerID=40&md5=c000884fdb4b114f77472743483801c3},
  abstract = {This theme issue aims to stimulate industry practitioners and researchers to reflect on what future release-engineering practices and tools could look like and how they could evolve out of more-advanced forms of current release engineering. Each of the four articles in this issue highlights a different facet of release engineering, with two articles focusing on fundamental technologies and practices and two articles discussing new application domains. © 1984-2012 IEEE.},
  key = {Adams201822},
  pages = {22-25},
  journal = {IEEE Software},
  number = {2},
  volume = {35},
  note = {cited By 0}
}
@article{laukkanen2018a,
  title = {Comparison of release engineering practices in a large mature company and a startup},
  author = {Laukkanen, E. and Paasivaara, M. and Itkonen, J. and Lassenius, C.},
  year = {2018},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85044460784&doi=10.1007%2fs10664-018-9616-7&partnerID=40&md5=dcca7b080050cb81ac889e6eede2b3cc},
  abstract = {Modern release engineering practices provide multiple benefits for software companies, but organizations have struggled when trying to adopt the most advanced practices, such as continuous delivery. It is not known in which contexts the most advanced practices are applicable and what can be achieved by adopting them. In this study, we discuss the effect of the organizational context on adopted release engineering practices and what outcomes are achieved with the practices. We study two organizational contexts: the startup and the large mature company context. The effect of the product context is mitigated by studying two case organizations with similar products, a rare research opportunity. We performed 18 interviews with various roles in the case organizations. The number of production environments, the number of customers, the control over the production environment, the available resources, the organization size and the distribution of the organization affected the release engineering practices and the ability to release frequently. Having less internal verification and more customer verification enabled fast feedback and customer experimentation in the startup context, but increased the number of production defects. However, having more internal verification in the large mature company context surprisingly did not prevent production defects. The organizational context had a large effect on how achievable modern release engineering practices, such as continuous delivery, were. In the startup context, the lack of resources was the main factor hindering the improvement of release engineering practices, while in the large mature company context, the number of stakeholders and products were the main factors. © 2018 The Author(s)},
  key = {Laukkanen20181},
  pages = {1-43},
  journal = {Empirical Software Engineering},
  note = {cited By 0; Article in Press}
}
@article{souza2015a,
  title = {Rapid releases and patch backouts: A software analytics approach},
  author = {Souza, R. and Chavez, C. and Bittencourt, R.A.},
  year = {2015},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84925218343&doi=10.1109%2fMS.2015.30&partnerID=40&md5=d624ac5b06a61704543a6d72af3981a1},
  abstract = {Mozilla's decision to release a new version of its products every six weeks (instead of every year) profoundly affected developers and users and was accompanied by significant changes in the release process. Were such changes enough to allow Mozilla to move faster without breaking things? What lessons can be learned from Mozilla's adoption of rapid releases? To answer these questions, researchers analyzed tens of thousands of commits and bug reports from Firefox and talked to its developers. The results show that, because of integration repositories, build sheriffs, and better testing tools, broken patches were backed out (reverted) earlier, rendering the release process more stable. © 2015 IEEE.},
  key = {Souza201589},
  pages = {89-96},
  journal = {IEEE Software},
  number = {2},
  volume = {32},
  note = {cited By 9}
}
@inproceedings{fujibayashi2017a,
  title = {Does the release cycle of a library project influence when it is adopted by a client project?},
  author = {Fujibayashi, D. and Ihara, A. and Suwa, H. and Kula, R.G. and Matsumoto, K.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85018384049&doi=10.1109%2fSANER.2017.7884681&partnerID=40&md5=83955b8bec9726f3eb1bc751b3c5f2f8},
  abstract = {A key goal of this research is to understand the relationship between adoption of software library versions and its release cycle. In detail, we conducted an empirical study of the release cycle of 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our preliminary findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. © 2017 IEEE.},
  key = {Fujibayashi2017569},
  pages = {569-570},
  journal = {SANER 2017 - 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering},
  note = {cited By 0}
}
@inproceedings{claes2017a,
  title = {Abnormal Working Hours: Effect of Rapid Releases and Implications to Work Content},
  author = {Claes, M. and Mantyla, M. and Kuutila, M. and Adams, B.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85026506528&doi=10.1109%2fMSR.2017.3&partnerID=40&md5=2da8fa8a15b9ffb4b1969663af15ecac},
  abstract = {During the past years, overload at work leading to psychological diseases, such as burnouts, have drawn more public attention. This paper is a preliminary step toward an analysis of the work patterns and possible indicators of overload and time pressure on software developers with mining software repositories approach. We explore the working pattern of developers in the context of Mozilla Firefox, a large and long-lived open source project. To that end we investigate the impact of the move from traditional to rapid release cycle on work pattern. Moreover we compare Mozilla Firefox work pattern with another Mozilla product, Firefox OS, which has a different release cycle than Firefox. We find that both projects exhibit healthy working patterns, i.e. lower activity during the weekends and outside of office hours. Firefox experiences proportionally more activity on weekends than Firefox OS (Cohen's d = 0.94). We find that switching to rapid releases has reduced weekend work (Cohen's d = 1.43) and working during the night (Cohen's d = 0.45). This result holds even when we limit the analyzes on the hired resources, i.e. considering only individuals with Mozilla foundation email address, although, the effect sizes are smaller for weekends (Cohen's d = 0.64) and nights (Cohen's d = 0.23). Moreover, we use dissimilarity word clouds and find that work during the weekend is more technical while work during the week expresses more positive sentiment with words like 'good' and 'nice'. Our results suggest that moving to rapid releases have positive impact on the work health and work-life-balance of software engineers. However, caution is needed as our results are based on a limited set of quantitative data from a single organization. © 2017 IEEE.},
  key = {Claes2017243},
  pages = {243-247},
  journal = {IEEE International Working Conference on Mining Software Repositories},
  note = {cited By 3}
}
@article{karvonen2017a,
  title = {Systematic literature review on the impacts of agile release engineering practices},
  author = {Karvonen, T. and Behutiye, W. and Oivo, M. and Kuvaja, P.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85028272067&doi=10.1016%2fj.infsof.2017.01.009&partnerID=40&md5=001c120eea2481c21dae5a551b44dd39},
  abstract = {Context Agile release engineering (ARE) practices are designed to deliver software faster and cheaper to end users; hence, claims of such impacts should be validated by rigorous and relevant empirical studies. Objective The study objective was to analyze both direct and indirect impacts of ARE practices as well as to determine how they have been empirically studied. Method The study applied the systematic literature review research method. ARE practices were identified in empirical studies by searching articles for “rapid release,” “continuous integration,” “continuous delivery,” and “continuous deployment.” We systematically analyzed 619 articles and selected 71 primary studies for deeper investigation. The impacts of ARE practices were analyzed from three viewpoints: impacts associated with adoption of the practice, prevalence of the practice, and success of software development. Results The results indicated that ARE practices can create shorter lead times and better communication within and between development teams. However, challenges and drawbacks were also found in change management, software quality assurance, and stakeholder acceptance. The analysis revealed that 33 out of 71 primary studies were casual experience reports that had neither an explicit research method nor a data collection approach specified, and 23 out of 38 empirical studies applied qualitative methods, such as interviews, among practitioners. Additionally, 12 studies applied quantitative methods, such as mining of software repositories. Only three empirical studies combined these research approaches. Conclusion ARE practices can contribute to improved efficiency of the development process. Moreover, release stakeholders can develop a better understanding of the software project's status. Future empirical studies should consider the comprehensive reporting of the context and how the practice is implemented instead of merely referring to usage of the practice. In addition, different stakeholder points of view, such as customer perceptions regarding ARE practices, still clearly require further research. © 2017 Elsevier B.V.},
  key = {Karvonen201787},
  pages = {87-100},
  journal = {Information and Software Technology},
  volume = {86},
  note = {cited By 5}
}
@inproceedings{castelluccio2017a,
  title = {Is it safe to uplift this patch? An empirical study on mozilla firefox},
  author = {Castelluccio, M. and An, L. and Khomh, F.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85040634374&doi=10.1109%2fICSME.2017.82&partnerID=40&md5=db36b40c2534743b53a2379157b50a59},
  abstract = {In rapid release development processes, patches that fix critical issues, or implement high-value features are often promoted directly from the development channel to a stabilization channel, potentially skipping one or more stabilization channels. This practice is called patch uplift. Patch uplift is risky, because patches that are rushed through the stabilization phase can end up introducing regressions in the code. This paper examines patch uplift operations at Mozilla, with the aim to identify the characteristics of uplifted patches that introduce regressions. Through statistical and manual analyses, we quantitatively and qualitatively investigate the reasons behind patch uplift decisions and the characteristics of uplifted patches that introduced regressions. Additionally, we interviewed three Mozilla release managers to understand organizational factors that affect patch uplift decisions and outcomes. Results show that most patches are uplifted because of a wrong functionality or a crash. Uplifted patches that lead to faults tend to have larger patch size, and most of the faults are due to semantic or memory errors in the patches. Also, release managers are more inclined to accept patch uplift requests that concern certain specific components, and-or that are submitted by certain specific developers. © 2017 IEEE.},
  key = {Castelluccio2017411},
  pages = {411-421},
  journal = {Proceedings - 2017 IEEE International Conference on Software Maintenance and Evolution, ICSME 2017},
  note = {cited By 0}
}
@inproceedings{kerzazi2013a,
  title = {Kanbanize the release engineering process},
  author = {Kerzazi, N. and Robillard, P.N.},
  year = {2013},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84886059813&doi=10.1109%2fRELENG.2013.6607689&partnerID=40\&md5=73eb9fc8ca1f9b6568975ff0c054308c},
  abstract = {Release management process must be adapted when IT organizations scale up to avoid discontinuity at the release flow and to preserve the software quality. This paper reports on means to improve the release process in a large-scale project. It discusses the rationale behind adopting Kanban principles for release management, how to implement these principles within a transitional approach, and what are the benefits. The paper discusses the post-transitional product to assess the status of the outcomes. © 2013 IEEE.},
  key = {Kerzazi20139},
  pages = {9-12},
  journal = {2013 1st International Workshop on Release Engineering, RELENG 2013 - Proceedings},
  note = {cited By 3}
}
@article{kaur2019a,
  title = {On Understanding the Release Patterns of Open Source Java Projects},
  author = {Kaur, A. and Vig, V.},
  year = {2019},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85049941993&doi=10.1007%2f978-981-10-8055-5_2&partnerID=40&md5=7a255f14762205c60f618cfb97569650},
  abstract = {Release length is of great significance to companies as well as to researchers as it provides a deeper insight into the rules and practices followed by the applications. It has been observed that many Open Source projects follow agile practices of parallel development and Rapid Releases (RR) but, very few studies till date, have analyzed release patterns of these Open Source projects. This paper analyzes ten Open Source Java projects (Apache Server Foundation) comprising 718 releases to study the evolution of release lengths. The results of the study show that: (1) eight out of ten datasets followed RR models. (2) None of these datasets followed RR models since their first release. (3) The average release length was found to be four months for major versions and one month for minor versions (exceptions removed). (4) There exists a negative correlation between number of contributors and release length. © 2019, Springer Nature Singapore Pte Ltd.},
  key = {Kaur20199},
  pages = {9-18},
  journal = {Advances in Intelligent Systems and Computing},
  volume = {711},
  note = {cited By 0}
}
@inproceedings{teixeira2017a,
  title = {Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management},
  author = {Teixeira, Jose},
  year = {2017},
  url = {http://doi.org/10.1007/978-3-319-57735-7_16},
  abstract = {The dictum of ``Release early, release often.'' by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. Nevertheless, there are very few empirical studies addressing release management in open source software development. It is already known that most open source software communities adopt either feature-based or time-based release strategies. Each of these has its advantages and disadvantages that are context-specific. Recent research reported that many prominent open source software projects have moved from feature-based to time-based releases. In this longitudinal case study, we narrate how OpenStack shifted towards a liberal six-month release cycle. If prior research discussed why projects should adopt time-based releases and how they can adopt such a strategy, we discuss how OpenStack adapted its software development processes, its organizational design and its tools toward a hybrid release management strategy --- a strive for balancing the benefits and drawbacks of feature-based and time-based release strategies.},
  doi = {10.1007/978-3-319-57735-7_16},
  editors = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Robles, Gregorio and Zacchiroli, Stefano},
  booktitle = {Open Source Systems: Towards Robust Practices},
  publisher = {Springer International Publishing},
  address = {Cham},
  pages = {167--181},
  note = {Paper extracted manually from book at URL.}
}
@phdthesis{poo-caamano2016a,
  title = {Release management in free and open source software ecosystems},
  author = {Poo-Caama{\~n}o, Germ{\'a}n},
  year = {2016},
  url = {http://dspace.library.uvic.ca/handle/1828/7648},
  key = {poo2016release}
}
@article{mantyla2015a,
  title = {On rapid releases and software testing: a case study and a semi-systematic literature review},
  author = {M{\"a}ntyl{\"a}, Mika V. and Adams, Bram and Khomh, Foutse and Engstr{\"o}m, Emelie and Petersen, Kai},
  year = {2015},
  url = {https://doi.org/10.1007/s10664-014-9338-4},
  abstract = {Large open and closed source organizations like Google, Facebook and Mozilla are migrating their products towards rapid releases. While this allows faster time-to-market and user feedback, it also implies less time for testing and bug fixing. Since initial research results indeed show that rapid releases fix proportionally less reported bugs than traditional releases, this paper investigates the changes in software testing effort after moving to rapid releases in the context of a case study on Mozilla Firefox, and performs a semi-systematic literature review. The case study analyzes the results of 312,502 execution runs of the 1,547 mostly manual system-level test cases of Mozilla Firefox from 2006 to 2012 (5 major traditional and 9 major rapid releases), and triangulates our findings with a Mozilla QA engineer. We find that rapid releases have a narrower test scope that enables a deeper investigation of the features and regressions with the highest risk. Furthermore, rapid releases make testing more continuous and have proportionally smaller spikes before the main release. However, rapid releases make it more difficult to build a large testing community , and they decrease test suite diversity and make testing more deadline oriented. In addition, our semi-systematic literature review presents the benefits, problems and enablers of rapid releases from 24 papers found using systematic search queries and a similar amount of papers found through other means. The literature review shows that rapid releases are a prevalent industrial practice that are utilized even in some highly critical domains of software engineering, and that rapid releases originated from several software development methodologies such as agile, open source, lean and internet-speed software development. However, empirical studies proving evidence of the claimed advantages and disadvantages of rapid releases are scarce.},
  key = {Mäntylä2015},
  pages = {1384--1425},
  journal = {Empirical Software Engineering},
  number = {5},
  volume = {20},
  note = {Had found "https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=\&arnumber=7006390", this paper is second reference on page 2}
}
@inproceedings{plewnia2014a,
  title = {On the influence of release engineering on software reputation},
  author = {Plewnia, Christian and Dyck, Andrej and Lichter, Horst},
  year = {2014},
  key = {plewnia2014influence},
  booktitle = {Mountain View, CA, USA: In 2nd International Workshop on Release Engineering},
  note = {Had found "https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=\&arnumber=7006390", this paper is first reference on page 2}
}
@article{khomh2015a,
  title = {Understanding the impact of rapid releases on software quality},
  author = {Khomh, Foutse and Adams, Bram and Dhaliwal, Tejinder and Zou, Ying},
  year = {2015},
  url = {https://doi.org/10.1007/s10664-014-9308-x},
  abstract = {Many software companies are shifting from the traditional multi-month release cycle to shorter release cycles. For example, Google Chrome and Mozilla Firefox release new versions every 6 weeks. These shorter release cycles reduce the users' waiting time for a new release and offer better feedback and marketing opportunities to companies, but it is unclear if the quality of the software product improves as well, since developers and testers are under more pressure. In this paper, we extend our previous empirical study of Mozilla Firefox on the impact of rapid releases on quality assurance with feedback by Mozilla project members. The study compares crash rates, median uptime, and the proportion of pre- and post-release bugs in traditional releases with those in rapid releases, and we also analyze the source code changes made by developers to identify potential changes in the development process. We found that (1) with shorter release cycles, users do not experience significantly more pre- or post-release bugs (percentage-wise) and (2) bugs are fixed faster, yet (3) users experience these bugs earlier during software execution (the program crashes earlier). Increased integration activity and propagation of harder bugs to later versions account for some of these findings. Overall, our case study suggests that a clear release engineering process with thorough automation is one of the major challenges when switching to rapid releases.},
  key = {Khomh2015},
  pages = {336--373},
  journal = {Empirical Software Engineering},
  number = {2},
  volume = {20}
}
@inproceedings{khomh2012a,
  title = {Do Faster Releases Improve Software Quality?: An Empirical Case Study of Mozilla Firefox},
  author = {Khomh, Foutse and Dhaliwal, Tejinder and Zou, Ying and Adams, Bram},
  year = {2012},
  url = {http://dl.acm.org/citation.cfm?id=2664446.2664475},
  keywords = {bugs, release cycle, software quality, software release, testing},
  key = {Khomh:2012:FRI:2664446.2664475},
  booktitle = {Proceedings of the 9th IEEE Working Conference on Mining Software Repositories},
  publisher = {IEEE Press},
  address = {Piscataway, NJ, USA},
  series = {MSR '12},
  pages = {179--188}
}
@inproceedings{da2014a,
  title = {An Empirical Study of Delays in the Integration of Addressed Issues},
  author = {da Costa, D. A. and Abebe, S. L. and Mcintosh, S. and Kulesza, U. and Hassan, A. E.},
  year = {2014},
  url = {https://doi.org/10.1109/ICSME.2014.50},
  keywords = {sensitivity analysis;software engineering;empirical analysis;software engineering;addressed issue integration;ArgoUML project;Eclipse project;Firefox project;release cycle;ROC area;receiver operator curve area;integrator workload;influential factor;integration delay models;nonnegligible delays;software system;Delays;Databases;Software;Unified modeling language;Educational institutions;Receivers},
  key = {6976094},
  booktitle = {2014 IEEE International Conference on Software Maintenance and Evolution},
  pages = {281-290}
}
@inproceedings{da2016a,
  title = {The Impact of Switching to a Rapid Release Cycle on the Integration Delay of Addressed Issues - An Empirical Study of the Mozilla Firefox Project},
  author = {da Costa, D. A. and McIntosh, S. and Kulesza, U. and Hassan, A. E.},
  year = {2016},
  url = {https://doi.org/10.1109/MSR.2016.045},
  keywords = {project management;software development management;software projects release frequency;code integration phase;integration delay;Mozilla Firefox Project;rapid release cycle;Computer bugs;Software;Delays;Marine vehicles;History;Context;Delivery delay;Release engineering;Empirical study},
  key = {7832916},
  booktitle = {2016 IEEE/ACM 13th Working Conference on Mining Software Repositories (MSR)},
  pages = {374-385}
}
@inproceedings{adams2016a,
  title = {Modern release engineering in a nutshell--why researchers should care},
  author = {Adams, Bram and McIntosh, Shane},
  year = {2016},
  url = {https://doi.org/10.1109/SANER.2016.108},
  key = {adams2016modern},
  booktitle = {Software Analysis, Evolution, and Reengineering (SANER), 2016 IEEE 23rd International Conference on},
  organization = {IEEE},
  pages = {78--90},
  volume = {5},
}
@article{laukkanen2017a,
  title = {Problems, causes and solutions when adopting continuous delivery—A systematic literature review},
  author = {Laukkanen, Eero and Itkonen, Juha and Lassenius, Casper},
  year = {2017},
  key = {laukkanen2017problems},
  publisher = {Elsevier},
  pages = {55--79},
  journal = {Information and Software Technology},
  volume = {82}
}

% END Release Engineering

@article{hyrynsalmi2012app,
  title={App store, marketplace, play! an analysis of multi-homing in mobile software ecosystems},
  author={Hyrynsalmi, Sami and M{\"a}kil{\"a}, Tuomas and J{\"a}rvi, Antero and Suominen, Arho and Sepp{\"a}nen, Marko and Knuutila, Timo},
  year={2012}
}

@article{genc2017systematic,
  title={A systematic literature review: Opinion mining studies from mobile app store user reviews},
  author={Genc-Nayebi, Necmiye and Abran, Alain},
  journal={Journal of Systems and Software},
  volume={125},
  pages={207--219},
  year={2017},
  publisher={Elsevier}
}

@inproceedings{di2016would,
  title={What would users change in my app? summarizing app reviews for recommending software changes},
  author={Di Sorbo, Andrea and Panichella, Sebastiano and Alexandru, Carol V and Shimagaki, Junji and Visaggio, Corrado A and Canfora, Gerardo and Gall, Harald C},
  booktitle={Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering},
  pages={499--510},
  year={2016},
  organization={ACM}
}

@article{hyrynsalmi2012app,
  title={App store, marketplace, play! an analysis of multi-homing in mobile software ecosystems},
  author={Hyrynsalmi, Sami and M{\"a}kil{\"a}, Tuomas and J{\"a}rvi, Antero and Suominen, Arho and Sepp{\"a}nen, Marko and Knuutila, Timo},
  year={2012}
}

@inproceedings{LBB2013,
 author = {Linares-V\'{a}squez, Mario and Bavota, Gabriele and Bernal-C\'{a}rdenas, Carlos and Di Penta, Massimiliano and Oliveto, Rocco and Poshyvanyk, Denys},
 title = {API Change and Fault Proneness: A Threat to the Success of Android Apps},
 booktitle = {Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering},
 series = {ESEC/FSE 2013},
 year = {2013},
 isbn = {978-1-4503-2237-9},
 location = {Saint Petersburg, Russia},
 pages = {477--487},
 numpages = {11},
 url = {http://doi.acm.org/10.1145/2491411.2491428},
 doi = {10.1145/2491411.2491428},
 acmid = {2491428},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {API changes, Android, Empirical Studies, Mining Software Repositories},
}

@ARTICLE{BLB2015,
author={G. Bavota and M. Linares-Vásquez and C. E. Bernal-Cárdenas and M. D. Penta and R. Oliveto and D. Poshyvanyk},
journal={IEEE Transactions on Software Engineering},
title={The Impact of API Change- and Fault-Proneness on the User Ratings of Android Apps},
year={2015},
volume={41},
number={4},
pages={384-407},
keywords={application program interfaces;data mining;mobile computing;program debugging;software fault tolerance;system recovery;API change-proneness;API fault-proneness;user ratings;Android Apps;mobile Apps market;information technology;software repository mining;Androids;Humanoid robots;Software;History;Computer bugs;Educational institutions;Electronic mail;Mining software repositories;empirical studies;android;API changes;Mining software repositories;empirical studies;android;API changes},
doi={10.1109/TSE.2014.2367027},
ISSN={0098-5589},
month={April},}

@INPROCEEDINGS{PSG2015,
author={S. Panichella and A. Di Sorbo and E. Guzman and C. A. Visaggio and G. Canfora and H. C. Gall},
booktitle={2015 IEEE International Conference on Software Maintenance and Evolution (ICSME)},
title={How can i improve my app? Classifying user reviews for software maintenance and evolution},
year={2015},
volume={},
number={},
pages={281-290},
keywords={natural language processing;pattern classification;software maintenance;text analysis;user review classification;software maintenance;software evolution;app stores;review comments;star ratings;user feedback identification;app review classification;natural language processing;text analysis;sentiment analysis;Taxonomy;Software maintenance;Feature extraction;Natural language processing;Mobile communication;Maintenance engineering;Text analysis;User Reviews;Mobile Applications;Natural Language Processing;Sentiment Analysis;Text classification},
doi={10.1109/ICSM.2015.7332474},
ISSN={},
month={Sept},}

@Book{xie2015,
  title = {Dynamic Documents with {R} and knitr},
  author = {Yihui Xie},
  publisher = {Chapman and Hall/CRC},
  address = {Boca Raton, Florida},
  year = {2015},
  edition = {2nd},
  note = {ISBN 978-1498716963},
  url = {http://yihui.name/knitr/},
}

@TechReport{kitchenham2007,
  author      = {Kitchenham},
  title       = {Guidelines for performing Systematic Literature Reviews in Software Engineering},
  institution = {Keele University; University of Durham},
  year        = {2007},
}

@incollection{fagan2002design,
  title={Design and code inspections to reduce errors in program development},
  author={Fagan, Michael},
  booktitle={Software pioneers},
  pages={575--607},
  year={2002},
  publisher={Springer}
}

@inproceedings{bacchelli2013expectations,
  title={Expectations, outcomes, and challenges of modern code review},
  author={Bacchelli, Alberto and Bird, Christian},
  booktitle={Proceedings of the 2013 international conference on software engineering},
  pages={712--721},
  year={2013},
  organization={IEEE Press}
}

@inproceedings{beller2014modern,
  title={Modern code reviews in open-source projects: Which problems do they fix?},
  author={Beller, Moritz and Bacchelli, Alberto and Zaidman, Andy and Juergens, Elmar},
  booktitle={Proceedings of the 11th working conference on mining software repositories},
  pages={202--211},
  year={2014},
  organization={ACM}
}

@inproceedings{gousios2014exploratory,
  title={An exploratory study of the pull-based software development model},
  author={Gousios, Georgios and Pinzger, Martin and Deursen, Arie van},
  booktitle={Proceedings of the 36th International Conference on Software Engineering},
  pages={345--355},
  year={2014},
  organization={ACM}
}

@inproceedings{mcintosh2014impact,
  title={The impact of code review coverage and code review participation on software quality: A case study of the qt, vtk, and itk projects},
  author={McIntosh, Shane and Kamei, Yasutaka and Adams, Bram and Hassan, Ahmed E},
  booktitle={Proceedings of the 11th Working Conference on Mining Software Repositories},
  pages={192--201},
  year={2014},
  organization={ACM}
}

@inproceedings{bird2015lessons,
  title={Lessons learned from building and deploying a code review analytics platform},
  author={Bird, Christian and Carnahan, Trevor and Greiler, Michaela},
  booktitle={Proceedings of the 12th Working Conference on Mining Software Repositories},
  pages={191--201},
  year={2015},
  organization={IEEE Press}
}

@inproceedings{czerwonka2015code,
  title={Code reviews do not find bugs: how the current code review best practice slows us down},
  author={Czerwonka, Jacek and Greiler, Michaela and Tilford, Jack},
  booktitle={Proceedings of the 37th International Conference on Software Engineering-Volume 2},
  pages={27--28},
  year={2015},
  organization={IEEE Press}
}

@inproceedings{baysal2013influence,
  title={The influence of non-technical factors on code review},
  author={Baysal, Olga and Kononenko, Oleksii and Holmes, Reid and Godfrey, Michael W},
  booktitle={Reverse Engineering (WCRE), 2013 20th Working Conference on},
  pages={122--131},
  year={2013},
  organization={IEEE}
}

@inproceedings{thongtanunam2015should,
  title={Who should review my code? A file location-based code-reviewer recommendation approach for modern code review},
  author={Thongtanunam, Patanamon and Tantithamthavorn, Chakkrit and Kula, Raula Gaikovina and Yoshida, Norihiro and Iida, Hajimu and Matsumoto, Ken-ichi},
  booktitle={Software Analysis, Evolution and Reengineering (SANER), 2015 IEEE 22nd International Conference on},
  pages={141--150},
  year={2015},
  organization={IEEE}
}

@inproceedings{xia2015should,
  title={Who should review this change?: Putting text and file location analyses together for more accurate recommendations},
  author={Xia, Xin and Lo, David and Wang, Xinyu and Yang, Xiaohu},
  booktitle={Software Maintenance and Evolution (ICSME), 2015 IEEE International Conference on},
  pages={261--270},
  year={2015},
  organization={IEEE}
}

@article{zanjani2016automatically,
  title={Automatically recommending peer reviewers in modern code review},
  author={Zanjani, Motahareh Bahrami and Kagdi, Huzefa and Bird, Christian},
  journal={IEEE Transactions on Software Engineering},
  volume={42},
  number={6},
  pages={530--543},
  year={2016},
  publisher={IEEE}
}

@inproceedings{thongtanunam2016revisiting,
  title={Revisiting code ownership and its relationship with software quality in the scope of modern code review},
  author={Thongtanunam, Patanamon and McIntosh, Shane and Hassan, Ahmed E and Iida, Hajimu},
  booktitle={Proceedings of the 38th international conference on software engineering},
  pages={1039--1050},
  year={2016},
  organization={ACM}
}

@article{baysal2016investigating,
  title={Investigating technical and non-technical factors influencing modern code review},
  author={Baysal, Olga and Kononenko, Oleksii and Holmes, Reid and Godfrey, Michael W},
  journal={Empirical Software Engineering},
  volume={21},
  number={3},
  pages={932--959},
  year={2016},
  publisher={Springer}
}

@inproceedings{bosu2013impact,
  title={Impact of peer code review on peer impression formation: A survey},
  author={Bosu, Amiangshu and Carver, Jeffrey C},
  booktitle={Empirical Software Engineering and Measurement, 2013 ACM/IEEE International Symposium on},
  pages={133--142},
  year={2013},
  organization={IEEE}
}

@inproceedings{baum2017choice,
  title={The choice of code review process: A survey on the state of the practice},
  author={Baum, Tobias and Le{\ss}mann, Hendrik and Schneider, Kurt},
  booktitle={International Conference on Product-Focused Software Process Improvement},
  pages={111--127},
  year={2017},
  organization={Springer}
}

@article{ciolkowski2003software,
  title={Software reviews: The state of the practice},
  author={Ciolkowski, Marcus and Laitenberger, Oliver and Biffl, Stefan},
  journal={IEEE software},
  number={6},
  pages={46--51},
  year={2003},
  publisher={IEEE}
}

@inproceedings{baum2016faceted,
  title={A faceted classification scheme for change-based industrial code review processes},
  author={Baum, Tobias and Liskin, Olga and Niklas, Kai and Schneider, Kurt},
  booktitle={Software Quality, Reliability and Security (QRS), 2016 IEEE International Conference on},
  pages={74--85},
  year={2016},
  organization={IEEE}
}

@article{cohen2010modern,
  title={Modern code review},
  author={Cohen, Jason},
  journal={Making Software: What Really Works, and Why We Believe It},
  pages={329--336},
  year={2010},
  publisher={" O'Reilly Media, Inc."}
}

@article{mcintosh2016empirical,
  title={An empirical study of the impact of modern code review practices on software quality},
  author={McIntosh, Shane and Kamei, Yasutaka and Adams, Bram and Hassan, Ahmed E},
  journal={Empirical Software Engineering},
  volume={21},
  number={5},
  pages={2146--2189},
  year={2016},
  publisher={Springer}
}

@inproceedings{thongtanunam2014reda,
  title={Reda: A web-based visualization tool for analyzing modern code review dataset},
  author={Thongtanunam, Patanamon and Yang, Xin and Yoshida, Norihiro and Kula, Raula Gaikovina and Cruz, Ana Erika Camargo and Fujiwara, Kenji and Iida, Hajimu},
  booktitle={Software Maintenance and Evolution (ICSME), 2014 IEEE International Conference on},
  pages={605--608},
  year={2014},
  organization={IEEE}
}

@article{thongtanunam2017review,
  title={Review participation in modern code review},
  author={Thongtanunam, Patanamon and McIntosh, Shane and Hassan, Ahmed E and Iida, Hajimu},
  journal={Empirical Software Engineering},
  volume={22},
  number={2},
  pages={768--817},
  year={2017},
  publisher={Springer}
}

@inproceedings{hamasaki2013does,
  title={Who does what during a code review? datasets of oss peer review repositories},
  author={Hamasaki, Kazuki and Kula, Raula Gaikovina and Yoshida, Norihiro and Cruz, AE and Fujiwara, Kenji and Iida, Hajimu},
  booktitle={Proceedings of the 10th Working Conference on Mining Software Repositories},
  pages={49--52},
  year={2013},
  organization={IEEE Press}
}

%% BEGIN chart-increasing-keyboard-Analytics

% Application is from 2014, this is the grant.
@misc{bird2017predicting,
  title={Predicting software build errors},
  author={Bird, Christian and Zimmermann, Thomas},
  year={2017},
  month=jan # "~10",
  publisher={Google Patents},
  note={US Patent 9,542,176}
}

@inproceedings{beller2017oops,
  title={Oops, my tests broke the build: An explorative analysis of Travis CI with GitHub},
  author={Beller, Moritz and Gousios, Georgios and Zaidman, Andy},
  booktitle={Mining Software Repositories (MSR), 2017 IEEE/ACM 14th International Conference on},
  pages={356--367},
  year={2017},
  organization={IEEE}
}

@inproceedings{rausch2017empirical,
  title={An empirical analysis of build failures in the continuous integration workflows of Java-based open-source software},
  author={Rausch, Thomas and Hummer, Waldemar and Leitner, Philipp and Schulte, Stefan},
  booktitle={Proceedings of the 14th International Conference on Mining Software Repositories},
  pages={345--355},
  year={2017},
  organization={IEEE Press}
}

@inproceedings{beller2017travistorrent,
  title={Travistorrent: Synthesizing travis ci and github for full-stack research on continuous integration},
  author={Beller, Moritz and Gousios, Georgios and Zaidman, Andy},
  booktitle={Proceedings of the 14th International Conference on Mining Software Repositories},
  pages={447--450},
  year={2017},
  organization={IEEE press}
}

@article{pinto2018work,
  title={Work Practices and Challenges in Continuous Integration: A Survey with Travis CI Users},
  author={Pinto, Gustavo and Rebou{\c{c}}as, Fernando Castor Rodrigo Bonifacio Marcel},
  year={2018}
}

@inproceedings{zhao2017impact,
  title={The impact of continuous integration on other software development practices: a large-scale empirical study},
  author={Zhao, Yangyang and Serebrenik, Alexander and Zhou, Yuming and Filkov, Vladimir and Vasilescu, Bogdan},
  booktitle={Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering},
  pages={60--71},
  year={2017},
  organization={IEEE Press}
}

@article{widder2018m,
  title={I'im Leaving You, Travis: A Continuous Integration Breakup Story},
  author={Widder, David Gray and Hilton, Michael and K{\"a}stner, Christian and Vasilescu, Bogdan},
  year={2018}
}

@inproceedings{hilton2016usage,
  title={Usage, costs, and benefits of continuous integration in open-source projects},
  author={Hilton, Michael and Tunnell, Timothy and Huang, Kai and Marinov, Darko and Dig, Danny},
  booktitle={Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering},
  pages={426--437},
  year={2016},
  organization={ACM}
}

@inproceedings{vassallo2017tale,
  title={A tale of CI build failures: An open source and a financial organization perspective},
  author={Vassallo, Carmine and Schermann, Gerald and Zampetti, Fiorella and Romano, Daniele and Leitner, Philipp and Zaidman, Andy and Di Penta, Massimiliano and Panichella, Sebastiano},
  booktitle={Software Maintenance and Evolution (ICSME), 2017 IEEE International Conference on},
  pages={183--193},
  year={2017},
  organization={IEEE}
}

@inproceedings{hassan2018hirebuild,
  title={HireBuild: an automatic approach to history-driven repair of build scripts},
  author={Hassan, Foyzul and Wang, Xiaoyin},
  booktitle={Proceedings of the 40th International Conference on Software Engineering},
  pages={1078--1089},
  year={2018},
  organization={ACM}
}

@article{vassallo2018break,
  title={Un-Break My Build: Assisting Developers with Build Repair Hints},
  author={Vassallo, Carmine and Proksch, Sebastian and Zemp, Timothy and Gall, Harald C},
  year={2018}
}

@inproceedings{zampetti2017open,
  title={How open source projects use static code analysis tools in continuous integration pipelines},
  author={Zampetti, Fiorella and Scalabrino, Simone and Oliveto, Rocco and Canfora, Gerardo and Di Penta, Massimiliano},
  booktitle={Mining Software Repositories (MSR), 2017 IEEE/ACM 14th International Conference on},
  pages={334--344},
  year={2017},
  organization={IEEE}
}

@article{fowler2006continuous,
  title={Continuous integration},
  author={Fowler, Martin and Foemmel, Matthew},
  journal={Thought-Works) http://www. thoughtworks. com/Continuous Integration. pdf},
  volume={122},
  pages={14},
  year={2006}
}

@inproceedings{stolberg2009enabling,
  title={Enabling agile testing through continuous integration},
  author={Stolberg, Sean},
  booktitle={Agile Conference, 2009. AGILE'09.},
  pages={369--374},
  year={2009},
  organization={IEEE}
}

@article{baltes2018no,
  title={(No) Influence of Continuous Integration on the Commit Activity in GitHub Projects},
  author={Baltes, Sebastian and Knack, Jascha and Anastasiou, Daniel and Tymann, Ralf and Diehl, Stephan},
  journal={arXiv preprint arXiv:1802.08441},
  year={2018}
}

@article{santolucito2018statically,
  title={Statically Verifying Continuous Integration Configurations},
  author={Santolucito, Mark and Zhang, Jialu and Zhai, Ennan and Piskac, Ruzica},
  journal={arXiv preprint arXiv:1805.04473},
  year={2018}
}

@inproceedings{bisong2017built,
  title={Built to last or built too fast?: evaluating prediction models for build times},
  author={Bisong, Ekaba and Tran, Eric and Baysal, Olga},
  booktitle={Proceedings of the 14th International Conference on Mining Software Repositories},
  pages={487--490},
  year={2017},
  organization={IEEE Press}
}

@inproceedings{ni2018acona,
  title={ACONA: active online model adaptation for predicting continuous integration build failures},
  author={Ni, Ansong and Li, Ming},
  booktitle={Proceedings of the 40th International Conference on Software Engineering: Companion Proceeedings},
  pages={366--367},
  year={2018},
  organization={ACM}
}

%% END chart-increasing-keyboard-Analytics

@article{beller2017developer,
title={Developer testing in the ide: Patterns, beliefs, and behavior},
author={Beller, Moritz and Georgios, Gousios and Panichella, Annibale and Proksch, Sebastian and Amann, Sven and Zaidman, Andy},
journal={IEEE Transactions on Software Engineering},
number={1},
pages={1--1},
year={2017},
publisher={IEEE}
}

@article{zaidman2011studying,
title={Studying the co-evolution of production and test code in open source and industrial developer test processes through repository mining},
author={Zaidman, Andy and Van Rompaey, Bart and van Deursen, Arie and Demeyer, Serge},
journal={Empirical Software Engineering},
volume={16},
number={3},
pages={325--364},
year={2011},
publisher={Springer}
}

@inproceedings{pinto2012understanding,
title={Understanding myths and realities of test-suite evolution},
author={Pinto, Leandro Sales and Sinha, Saurabh and Orso, Alessandro},
booktitle={Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering},
pages={33},
year={2012},
organization={ACM}
}

@inproceedings{noor2015test,
title={Test case analytics: Mining test case traces to improve risk-driven testing},
author={Noor, Tanzeem Bin and Hemmati, Hadi},
booktitle={Software Analytics (SWAN), 2015 IEEE 1st International Workshop on},
pages={13--16},
year={2015},
organization={IEEE}
}

@inproceedings{leung2015testing,
title={Testing analytics on software variability},
author={Leung, Hareton KN and Lui, Kim Man},
booktitle={Software Analytics (SWAN), 2015 IEEE 1st International Workshop on},
pages={17--20},
year={2015},
organization={IEEE}
}

@inproceedings{haron2016TestAndDefect,
        author={Haron,N. H. and Syed-Mohamad,S. M.},
        editor={ },
        year={2016},
        title={Test and Defect Coverage Analytics Model for the assessment of software test adequacy},
        booktitle={2015 9th Malaysian Software Engineering Conference, MySEC 2015},
        pages={13-18},
        language={English},
        url={www.scopus.com},
}

@INPROCEEDINGS{supportingtestsuite,
author={M. Mirzaaghaei and F. Pastore and M. Pezze},
booktitle={2012 IEEE Fifth International Conference on Software Testing, Verification and Validation},
title={Supporting Test Suite Evolution through Test Case Adaptation},
year={2012},
volume={},
number={},
pages={231-240},
keywords={automatic test pattern generation;automatic test software;program testing;software maintenance;software prototyping;test case design;software development;software maintenance;software lifecycle;test case repairing;software evolution;test case generation;prototype implementation;Maintenance engineering;Software algorithms;Testing;Context;Software systems;Instruments;Software testing;Test case evolution;Test case maintenance},
doi={10.1109/ICST.2012.103},
ISSN={2159-4848},
month={April},}

@inproceedings{bevan2005,
        author={Bevan,J. and Whitehead Jr.,E. J. and Kim,S. and Godfrey,M.},
        editor={ },
        year={2005},
        title={Facilitating software evolution research with kenyon},
        booktitle={ESEC/FSE'05 - Proceedings of the Joint 10th European Software Engineering Conference (ESEC) and 13th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-13)},
        pages={177-186},
        note={Cited By :86},
        language={English},
        url={www.scopus.com},
}

@inproceedings{pinto2013,
author={Pinto,L. S. and Sinha,S. and Orso,A.},
editor={ },
year={2013},
title={TestEvol: A tool for analyzing test-suite evolution},
booktitle={Proceedings - International Conference on Software Engineering},
pages={1303-1306},
note={Cited By :1},
language={English},
url={www.scopus.com},
}

@INPROCEEDINGS{hurdugaci2012,
author={V. Hurdugaci and A. Zaidman},
booktitle={2012 16th European Conference on Software Maintenance and Reengineering},
title={Aiding Software Developers to Maintain Developer Tests},
year={2012},
volume={},
number={},
pages={11-20},
keywords={program testing;software maintenance;software quality;developer test;unit test;integration test;software maintenance;quality assurance;TestNForce;Production;Software;Indexes;Visualization;Testing;Programming;Educational institutions},
doi={10.1109/CSMR.2012.12},
ISSN={1534-5351},
month={March},}

@INPROCEEDINGS{marsavina2014,
author={C. Marsavina and D. Romano and A. Zaidman},
booktitle={2014 IEEE 14th International Working Conference on Source Code Analysis and Manipulation},
title={Studying Fine-Grained Co-evolution Patterns of Production and Test Code},
year={2014},
volume={},
number={},
pages={195-204},
keywords={data mining;program testing;public domain software;software engineering;fine-grained coevolution patterns;software development practices;test code;production code;coevolving test;mixed methods approach;open-source systems;association rule mining algorithm;Production;Association rules;Testing;Software systems;Statistical analysis;Educational institutions},
doi={10.1109/SCAM.2014.28},
ISSN={},
month={Sept},}

@ARTICLE{eick2001,
author={S. G. Eick and T. L. Graves and A. F. Karr and J. S. Marron and A. Mockus},
journal={IEEE Transactions on Software Engineering},
title={Does code decay? Assessing the evidence from change management data},
year={2001},
volume={27},
number={1},
pages={1-12},
keywords={software maintenance;software metrics;management of change;statistical analysis;code decay;change management data;large software systems evolution;software measurements;risk factors;data set;telephone switching system;perfective maintenance;software maintenance;statistical analysis;Software maintenance;Software systems;Hardware;Telephony;History;Statistical analysis;Computer Society;Software measurement;Switching systems;Operating systems},
doi={10.1109/32.895984},
ISSN={0098-5589},
month={Jan},}

@inproceedings{greiler2013,
        author={Greiler,M. and Zaidman,A. and Van Deursen,A. and Storey,M. -.},
        editor={ },
        year={2013},
        title={Strategies for avoiding text fixture smells during software evolution},
        booktitle={IEEE International Working Conference on Mining Software Repositories},
        pages={387-396},
        note={Cited By :12},
        language={English},
        url={www.scopus.com},
}

@INPROCEEDINGS{robinson2011,
author={B. Robinson and M. D. Ernst and J. H. Perkins and V. Augustine and N. Li},
booktitle={2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011)},
title={Scaling up automated test generation: Automatically generating maintainable regression unit tests for programs},
year={2011},
volume={},
number={},
pages={23-32},
keywords={program compilers;program debugging;program testing;regression analysis;software maintenance;automated test generation;maintainable regression unit tests;bugs;industrial system;mutation kill score;programs;Libraries;Software;Testing;Observers;Security;Databases;Context},
doi={10.1109/ASE.2011.6100059},
ISSN={1938-4300},
month={Nov},}

@article{bowring2014obsidian,
  title={Obsidian: Pattern-Based Unit Test Implementations},
  author={Bowring, James and Hegler, Hunter},
  journal={Journal of Software Engineering and Applications},
  volume={7},
  number={02},
  pages={94},
  year={2014},
  publisher={Scientific Research Publishing}
}

@inproceedings{shamshiri2018automatically,
  title={How Do Automatically Generated Unit Tests Influence Software Maintenance?},
  author={Shamshiri, Sina and Rojas, Jos{\'e} Miguel and Galeotti, Juan Pablo and Walkinshaw, Neil and Fraser, Gordon},
  booktitle={Software Testing, Verification and Validation (ICST), 2018 IEEE 11th International Conference on},
  pages={250--261},
  year={2018},
  organization={IEEE},
  doi={10.1109/ICST.2018.00033},
}

@inproceedings{dulz2013model,
  title={Model-based strategies for reducing the complexity of statistically generated test suites},
  author={Dulz, Winfried},
  booktitle={International Conference on Software Quality},
  pages={89--103},
  year={2013},
  organization={Springer}
}

@inproceedings{hemmati2018,
        author={Hemmati,H. and Sharifi,F.},
        editor={ },
        year={2018},
        title={Investigating NLP-Based Approaches for Predicting Manual Test Case Failure},
        booktitle={Proceedings - 2018 IEEE 11th International Conference on Software Testing, Verification and Validation, ICST 2018},
        pages={309-319},
        language={English},
        url={www.scopus.com},
}

@article{schneidewind2007,
        author={Schneidewind,N. F.},
        year={2007},
        title={Risk-driven software testing and reliability},
        journal={International Journal of Reliability, Quality and Safety Engineering},
        volume={14},
        number={2},
        pages={99-132},
        note={Cited By :10},
        language={English},
        url={www.scopus.com},
}

@book{vernotte2015,
        author={Vernotte,A. and Botea,C. and Legeard,B. and Molnar,A. and Peureux,F.},
        year={2015},
        title={Risk-driven vulnerability testing: Results from eHealth experiments using patterns and model-based approach},
        series={Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)},
        volume={9488},
        pages={93-109},
        language={English},
        url={www.scopus.com},
}

@book{atifi2017,
        author={Atifi,M. and Mamouni,A. and Marzak,A.},
        year={2017},
        title={A comparative study of software testing techniques},
        series={Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)},
        volume={10299 LNCS},
        pages={373-390},
        language={English},
        url={www.scopus.com},
}

@inproceedings{beller2015,
        author={Beller,M. and Gousios,G. and Panichella,A. and Zaidman,A.},
        editor={ },
        year={2015},
        title={When, how, and why developers (do not) test in their IDEs},
        booktitle={2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings},
        pages={179-190},
        note={Cited By :39},
        language={English},
        url={www.scopus.com},
}

@article{GAROUSI20131354,
title = "A survey of software testing practices in Canada",
journal = "Journal of Systems and Software",
volume = "86",
number = "5",
pages = "1354 - 1376",
year = "2013",
issn = "0164-1212",
doi = "https://doi.org/10.1016/j.jss.2012.12.051",
url = "http://www.sciencedirect.com/science/article/pii/S0164121212003561",
author = "Vahid Garousi and Junji Zhi",
keywords = "Survey, Software testing, Industry practices, Canada"
}

@incollection{moiz2017uncertainty,
  title={Uncertainty in Software Testing},
  author={Moiz, Salman Abdul},
  booktitle={Trends in Software Testing},
  pages={67--87},
  year={2017},
  publisher={Springer}
}

@article{cesar2017a,
  title = {Frequent Releases in Open Source Software: A Systematic Review},
  author = {Cesar Brand{\~a}o Gomes da Silva, Antonio and de Figueiredo Carneiro, Glauco and Brito e Abreu, Fernando and Pessoa Monteiro, Miguel},
  year = {2017},
  key = {cesar2017frequent},
  publisher = {Multidisciplinary Digital Publishing Institute},
  pages = {109},
  journal = {Information},
  number = {3},
  volume = {8}
}
@article{rodriguez2017a,
  title = {Continuous deployment of software intensive products and services: A systematic mapping study},
  author = {Rodr{\'\i}guez, Pilar and Haghighatkhah, Alireza and Lwakatare, Lucy Ellen and Teppola, Susanna and Suomalainen, Tanja and Eskeli, Juho and Karvonen, Teemu and Kuvaja, Pasi and Verner, June M and Oivo, Markku},
  year = {2017},
  key = {rodriguez2017continuous},
  publisher = {Elsevier},
  pages = {263--291},
  journal = {Journal of Systems and Software},
  volume = {123}
}
@inproceedings{dyck2015a,
  title = {Towards definitions for release engineering and devops},
  author = {Dyck, Andrej and Penners, Ralf and Lichter, Horst},
  year = {2015},
  url = {https://www2.swc.rwth-aachen.de/docs/RELENG2015/DevOpsVsRelEng.pdf},
  key = {dyck2015towards},
  booktitle = {Release Engineering (RELENG), 2015 IEEE/ACM 3rd International Workshop on},
  organization = {IEEE},
  pages = {3--3}
}

@article{spinellis2018a,
  title = {The Challenges and Practices of Release Engineering},
  author = {Spinellis, Diomidis},
  year = {2018},
  key = {spinellis2018challenges},
  publisher = {IEEE},
  pages = {4--7},
  journal = {IEEE Software},
  number = {2},
  volume = {35}
}
@article{chen2015a,
  title = {Continuous delivery: Huge benefits, but challenges too},
  author = {Chen, Lianping},
  year = {2015},
  key = {chen2015continuous},
  publisher = {IEEE},
  pages = {50--54},
  journal = {IEEE Software},
  number = {2},
  volume = {32}
}
@inproceedings{adams2015a,
  title = {3rd International Workshop on Release Engineering (RELENG 2015)},
  author = {Adams, B. and Bellomo, S. and Bird, C. and Khomh, F. and Moir, K.},
  year = {2015},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84951851911\&doi=10.1109%2fICSE.2015.321\&partnerID=40\&md5=4b9e0d9d5346e0b8926c9e2d34a7170d},
  abstract = {Release engineering deals with all activities inbetween regular development and actual usage of asoftware product by the end user, i.e., integration, build, testexecution, packaging and delivery of software. Although re-search on this topic goes back for decades, the increasing heterogeneity and variability of software products along withthe recent trend to reduce the release cycle to days or even hoursstarts to question some of the common beliefs and practicesof the field. For example, a project like Mozilla Firefox releasesevery 6 weeks, generating updates for dozens of existing Fire-fox versions on 5 desktop, 2 mobile and 3 mobile desktopplatforms, each of which for more than 80 locales. In this con-text, the International Workshop on Release Engineering(RELENG) aims to provide a highly interactive forum for re-searchers and practitioners to address the challenges of, findsolutions for and share experiences with release engineering, and to build connections between the various communities. © 2015 IEEE.},
  key = {Adams2015995},
  pages = {995-996},
  journal = {Proceedings - International Conference on Software Engineering},
  volume = {2},
  note = {cited By 0}
}
@article{adams2018a,
  title = {Release engineering 3.0},
  author = {Adams, B. and Bellomo, S. and Bird, C. and Debic, B. and Khomh, F. and Moir, K. and Oduinn, J.},
  year = {2018},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85043684495\&doi=10.1109%2fMS.2018.1661327\&partnerID=40\&md5=c000884fdb4b114f77472743483801c3},
  abstract = {This theme issue aims to stimulate industry practitioners and researchers to reflect on what future release-engineering practices and tools could look like and how they could evolve out of more-advanced forms of current release engineering. Each of the four articles in this issue highlights a different facet of release engineering, with two articles focusing on fundamental technologies and practices and two articles discussing new application domains. © 1984-2012 IEEE.},
  key = {Adams201822},
  pages = {22-25},
  journal = {IEEE Software},
  number = {2},
  volume = {35},
  note = {cited By 0}
}

@book{beck2003test,
  title={Test-driven development: by example},
  author={Beck, Kent},
  year={2003},
  publisher={Addison-Wesley Professional}
}

@article{ROMANO201764,
  title = "Findings from a multi-method study on test-driven development",
  journal = "Information and Software Technology",
  volume = "89",
  pages = "64 - 77",
  year = "2017",
  issn = "0950-5849",
  doi = "https://doi.org/10.1016/j.infsof.2017.03.010",
  url = "http://www.sciencedirect.com/science/article/pii/S0950584917302550",
  author = "Simone Romano and Davide Fucci and Giuseppe Scanniello and Burak Turhan and Natalia Juristo",
  keywords = "Ethnographically-informed study, Qualitative study, Test driven development"
}

@inproceedings{Beller:2015:DT:2819009.2819101,
  author = {Beller, Moritz and Gousios, Georgios and Zaidman, Andy},
  title = {How (Much) Do Developers Test?},
  booktitle = {Proceedings of the 37th International Conference on Software Engineering - Volume 2},
  series = {ICSE '15},
  year = {2015},
  location = {Florence, Italy},
  pages = {559--562},
  numpages = {4},
  url = {http://dl.acm.org/citation.cfm?id=2819009.2819101},
  acmid = {2819101},
  publisher = {IEEE Press},
  address = {Piscataway, NJ, USA}
}

@article{bouwers2012a,
 author = {Bouwers, Eric and Visser, Joost and van Deursen, Arie},
 title = {Getting What You Measure},
 journal = {Commun. ACM},
 issue_date = {July 2012},
 volume = {55},
 number = {7},
 month = jul,
 year = {2012},
 issn = {0001-0782},
 pages = {54--59},
 numpages = {6},
 url = {http://doi.acm.org/10.1145/2209249.2209266},
 doi = {10.1145/2209249.2209266},
 acmid = {2209266},
 publisher = {ACM},
 address = {New York, NY, USA},
}

@inproceedings{vasilescu2014continuous,
  title={Continuous integration in a social-coding world: Empirical evidence from GitHub},
  author={Vasilescu, Bogdan and Van Schuylenburg, Stef and Wulms, Jules and Serebrenik, Alexander and van den Brand, Mark GJ},
  booktitle={Software maintenance and evolution (icsme), 2014 ieee international conference on},
  pages={401--405},
  year={2014},
  organization={IEEE}
}

%---------Runtime and performance analytics-------------%
@inproceedings{OOC2017,
  title={A study on the energy consumption of Android app development approaches},
  author={Oliveira, Wellington and Oliveira, Renato and Castor, Fernando},
  booktitle={Mining Software Repositories (MSR), 2017 IEEE/ACM 14th International Conference on},
  pages={42--52},
  year={2017},
  organization={IEEE}
}

@inproceedings{LXC2014,
  title={Characterizing and detecting performance bugs for smartphone applications},
  author={Liu, Yepang and Xu, Chang and Cheung, Shing-Chi},
  booktitle={Proceedings of the 36th International Conference on Software Engineering},
  pages={1013--1024},
  year={2014},
  organization={ACM}
}

@inproceedings{PSCS2018,
  title={jStanley: placing a green thumb on Java collections},
  author={Pereira, Rui and Sim{\~a}o, Pedro and Cunha, J{\'a}come and Saraiva, Jo{\~a}o},
  booktitle={Proceedings of the 33rd ACM/IEEE International Conference on Automated Software Engineering},
  pages={856--859},
  year={2018},
  organization={ACM}
}

@inproceedings{GKLS2018,
  title={What are your programming language's energy-delay implications?},
  author={Georgiou, Stefanos and Kechagia, Maria and Louridas, Panos and Spinellis, Diomidis},
  booktitle={Proceedings of the 15th International Conference on Mining Software Repositories},
  pages={303--313},
  year={2018},
  organization={ACM}
}

@inproceedings{NPPPZL2017,
  title={Software-based energy profiling of android apps: Simple, efficient and reliable?},
  author={Di Nucci, Dario and Palomba, Fabio and Prota, Antonio and Panichella, Annibale and Zaidman, Andy and De Lucia, Andrea},
  booktitle={Software Analysis, Evolution and Reengineering (SANER), 2017 IEEE 24th International Conference on},
  pages={103--114},
  year={2017},
  organization={IEEE}
}

@article{PHA2016,
  title={What do programmers know about software energy consumption?},
  author={Pang, Candy and Hindle, Abram and Adams, Bram and Hassan, Ahmed E},
  journal={IEEE Software},
  volume={33},
  number={3},
  pages={83--89},
  year={2016},
  publisher={IEEE}
}

@article{BCBR2017,
  title={Energypatch: Repairing resource leaks to improve energy-efficiency of android apps},
  author={Banerjee, Abhijeet and Chong, Lee Kee and Ballabriga, Cl{\'e}ment and Roychoudhury, Abhik},
  journal={IEEE Transactions on Software Engineering},
  volume={44},
  number={5},
  pages={470--490},
  year={2018},
  publisher={IEEE}
}

@inproceedings{NPPPZL2017B,
  title={Petra: a software-based tool for estimating the energy profile of android applications},
  author={Di Nucci, Dario and Palomba, Fabio and Prota, Antonio and Panichella, Annibale and Zaidman, Andy and De Lucia, Andrea},
  booktitle={Proceedings of the 39th International Conference on Software Engineering Companion},
  pages={3--6},
  year={2017},
  organization={IEEE Press}
}

@inproceedings{LH2014,
  title={An investigation into energy-saving programming practices for android smartphone app development},
  author={Li, Ding and Halfond, William GJ},
  booktitle={Proceedings of the 3rd International Workshop on Green and Sustainable Software},
  pages={46--53},
  year={2014},
  organization={ACM}
}

@article{MSA2018,
  title={What can Android mobile app developers do about the energy consumption of machine learning?},
  author={McIntosh, Andrea and Hassan, Safwat and Hindle, Abram},
  journal={Empirical Software Engineering},
  pages={1--40},
  year={2018},
  publisher={Springer}
}

@article{SKHA2018,
  title={An App Performance Optimization Advisor for Mobile Device App Marketplaces},
  author={Saborido, Rub{\'e}n and Khomh, Foutse and Hindle, Abram and Alba, Enrique},
  journal={Sustainable Computing: Informatics and Systems},
  year={2018},
  publisher={Elsevier}
}

@inproceedings{MBZ2016,
  title={An empirical study of practitioners' perspectives on green software engineering},
  author={Manotas, Irene and Bird, Christian and Zhang, Rui and Shepherd, David and Jaspan, Ciera and Sadowski, Caitlin and Pollock, Lori and Clause, James},
  booktitle={Software Engineering (ICSE), 2016 IEEE/ACM 38th International Conference on},
  pages={237--248},
  year={2016},
  organization={IEEE}
}

@inproceedings{JBW2017,
  title={Awakening awareness on energy consumption in software engineering},
  author={Jagroep, Erik and Broekman, Jordy and Van Der Werf, Jan Martijn EM and Lago, Patricia and Brinkkemper, Sjaak and Blom, Leen and Van Vliet, Rob},
  booktitle={Software Engineering: Software Engineering in Society Track (ICSE-SEIS), 2017 IEEE/ACM 39th International Conference on},
  pages={76--85},
  year={2017},
  organization={IEEE}
}

@inproceedings{CA2017,
  title={Performance-based guidelines for energy efficient mobile applications},
  author={Cruz, Luis and Abreu, Rui},
  booktitle={Mobile Software Engineering and Systems (MOBILESoft), 2017 IEEE/ACM 4th International Conference on},
  pages={46--57},
  year={2017},
  organization={IEEE}
}

@inproceedings{AKG2015,
  title={How green are cloud patterns?},
  author={Abtahizadeh, S Amirhossein and Khomh, Foutse and Gu{\'e}h{\'e}neuc, Yann-Ga{\"e}l},
  booktitle={Computing and Communications Conference (IPCCC), 2015 IEEE 34th International Performance},
  pages={1--8},
}

@article{laukkanen2018a,
  title = {Comparison of release engineering practices in a large mature company and a startup},
  author = {Laukkanen, E. and Paasivaara, M. and Itkonen, J. and Lassenius, C.},
  year = {2018},
  key = {Laukkanen20181},
  pages = {1-43},
  journal = {Empirical Software Engineering},
  note = {cited By 0; Article in Press}
}

@article{souza2015a,
  title = {Rapid releases and patch backouts: A software analytics approach},
  author = {Souza, R. and Chavez, C. and Bittencourt, R.A.},
  year = {2015},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84925218343\&doi=10.1109%2fMS.2015.30\&partnerID=40\&md5=d624ac5b06a61704543a6d72af3981a1},
  abstract = {Mozilla's decision to release a new version of its products every six weeks (instead of every year) profoundly affected developers and users and was accompanied by significant changes in the release process. Were such changes enough to allow Mozilla to move faster without breaking things? What lessons can be learned from Mozilla's adoption of rapid releases? To answer these questions, researchers analyzed tens of thousands of commits and bug reports from Firefox and talked to its developers. The results show that, because of integration repositories, build sheriffs, and better testing tools, broken patches were backed out (reverted) earlier, rendering the release process more stable. © 2015 IEEE.},
  key = {Souza201589},
  pages = {89-96},
  journal = {IEEE Software},
  number = {2},
  volume = {32},
  note = {cited By 9}
}

@inproceedings{fujibayashi2017a,
  title = {Does the release cycle of a library project influence when it is adopted by a client project?},
  author = {Fujibayashi, D. and Ihara, A. and Suwa, H. and Kula, R.G. and Matsumoto, K.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85018384049\&doi=10.1109%2fSANER.2017.7884681\&partnerID=40\&md5=83955b8bec9726f3eb1bc751b3c5f2f8},
  abstract = {A key goal of this research is to understand the relationship between adoption of software library versions and its release cycle. In detail, we conducted an empirical study of the release cycle of 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our preliminary findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. © 2017 IEEE.},
  key = {Fujibayashi2017569},
  pages = {569-570},
  journal = {SANER 2017 - 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering},
  note = {cited By 0}
}

@inproceedings{claes2017a,
  title = {Abnormal Working Hours: Effect of Rapid Releases and Implications to Work Content},
  author = {Claes, M. and Mantyla, M. and Kuutila, M. and Adams, B.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85026506528\&doi=10.1109%2fMSR.2017.3\&partnerID=40\&md5=2da8fa8a15b9ffb4b1969663af15ecac},
  abstract = {During the past years, overload at work leading to psychological diseases, such as burnouts, have drawn more public attention. This paper is a preliminary step toward an analysis of the work patterns and possible indicators of overload and time pressure on software developers with mining software repositories approach. We explore the working pattern of developers in the context of Mozilla Firefox, a large and long-lived open source project. To that end we investigate the impact of the move from traditional to rapid release cycle on work pattern. Moreover we compare Mozilla Firefox work pattern with another Mozilla product, Firefox OS, which has a different release cycle than Firefox. We find that both projects exhibit healthy working patterns, i.e. lower activity during the weekends and outside of office hours. Firefox experiences proportionally more activity on weekends than Firefox OS (Cohen's d = 0.94). We find that switching to rapid releases has reduced weekend work (Cohen's d = 1.43) and working during the night (Cohen's d = 0.45). This result holds even when we limit the analyzes on the hired resources, i.e. considering only individuals with Mozilla foundation email address, although, the effect sizes are smaller for weekends (Cohen's d = 0.64) and nights (Cohen's d = 0.23). Moreover, we use dissimilarity word clouds and find that work during the weekend is more technical while work during the week expresses more positive sentiment with words like 'good' and 'nice'. Our results suggest that moving to rapid releases have positive impact on the work health and work-life-balance of software engineers. However, caution is needed as our results are based on a limited set of quantitative data from a single organization. © 2017 IEEE.},
  key = {Claes2017243},
  pages = {243-247},
  journal = {IEEE International Working Conference on Mining Software Repositories},
  note = {cited By 3}
}

@article{karvonen2017a,
  title = {Systematic literature review on the impacts of agile release engineering practices},
  author = {Karvonen, T. and Behutiye, W. and Oivo, M. and Kuvaja, P.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85028272067\&doi=10.1016%2fj.infsof.2017.01.009\&partnerID=40\&md5=001c120eea2481c21dae5a551b44dd39},
  abstract = {Context Agile release engineering (ARE) practices are designed to deliver software faster and cheaper to end users; hence, claims of such impacts should be validated by rigorous and relevant empirical studies. Objective The study objective was to analyze both direct and indirect impacts of ARE practices as well as to determine how they have been empirically studied. Method The study applied the systematic literature review research method. ARE practices were identified in empirical studies by searching articles for “rapid release,” “continuous integration,” “continuous delivery,” and “continuous deployment.” We systematically analyzed 619 articles and selected 71 primary studies for deeper investigation. The impacts of ARE practices were analyzed from three viewpoints: impacts associated with adoption of the practice, prevalence of the practice, and success of software development. Results The results indicated that ARE practices can create shorter lead times and better communication within and between development teams. However, challenges and drawbacks were also found in change management, software quality assurance, and stakeholder acceptance. The analysis revealed that 33 out of 71 primary studies were casual experience reports that had neither an explicit research method nor a data collection approach specified, and 23 out of 38 empirical studies applied qualitative methods, such as interviews, among practitioners. Additionally, 12 studies applied quantitative methods, such as mining of software repositories. Only three empirical studies combined these research approaches. Conclusion ARE practices can contribute to improved efficiency of the development process. Moreover, release stakeholders can develop a better understanding of the software project's status. Future empirical studies should consider the comprehensive reporting of the context and how the practice is implemented instead of merely referring to usage of the practice. In addition, different stakeholder points of view, such as customer perceptions regarding ARE practices, still clearly require further research. © 2017 Elsevier B.V.},
  key = {Karvonen201787},
  pages = {87-100},
  journal = {Information and Software Technology},
  volume = {86},
  note = {cited By 5}
}
@inproceedings{castelluccio2017a,
  title = {Is it safe to uplift this patch? An empirical study on mozilla firefox},
  author = {Castelluccio, M. and An, L. and Khomh, F.},
  year = {2017},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85040634374\&doi=10.1109%2fICSME.2017.82\&partnerID=40\&md5=db36b40c2534743b53a2379157b50a59},
  abstract = {In rapid release development processes, patches that fix critical issues, or implement high-value features are often promoted directly from the development channel to a stabilization channel, potentially skipping one or more stabilization channels. This practice is called patch uplift. Patch uplift is risky, because patches that are rushed through the stabilization phase can end up introducing regressions in the code. This paper examines patch uplift operations at Mozilla, with the aim to identify the characteristics of uplifted patches that introduce regressions. Through statistical and manual analyses, we quantitatively and qualitatively investigate the reasons behind patch uplift decisions and the characteristics of uplifted patches that introduced regressions. Additionally, we interviewed three Mozilla release managers to understand organizational factors that affect patch uplift decisions and outcomes. Results show that most patches are uplifted because of a wrong functionality or a crash. Uplifted patches that lead to faults tend to have larger patch size, and most of the faults are due to semantic or memory errors in the patches. Also, release managers are more inclined to accept patch uplift requests that concern certain specific components, and-or that are submitted by certain specific developers. © 2017 IEEE.},
  key = {Castelluccio2017411},
  pages = {411-421},
  journal = {Proceedings - 2017 IEEE International Conference on Software Maintenance and Evolution, ICSME 2017},
  note = {cited By 0}
}

@inproceedings{kerzazi2013a,
  title = {Kanbanize the release engineering process},
  author = {Kerzazi, N. and Robillard, P.N.},
  year = {2013},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-84886059813\&doi=10.1109%2fRELENG.2013.6607689\&partnerID=40\&md5=73eb9fc8ca1f9b6568975ff0c054308c},
  abstract = {Release management process must be adapted when IT organizations scale up to avoid discontinuity at the release flow and to preserve the software quality. This paper reports on means to improve the release process in a large-scale project. It discusses the rationale behind adopting Kanban principles for release management, how to implement these principles within a transitional approach, and what are the benefits. The paper discusses the post-transitional product to assess the status of the outcomes. © 2013 IEEE.},
  key = {Kerzazi20139},
  pages = {9-12},
  journal = {2013 1st International Workshop on Release Engineering, RELENG 2013 - Proceedings},
  note = {cited By 3}
}
@article{kaur2019a,
  title = {On Understanding the Release Patterns of Open Source Java Projects},
  author = {Kaur, A. and Vig, V.},
  year = {2019},
  url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85049941993\&doi=10.1007%2f978-981-10-8055-5_2\&partnerID=40\&md5=7a255f14762205c60f618cfb97569650},
  abstract = {Release length is of great significance to companies as well as to researchers as it provides a deeper insight into the rules and practices followed by the applications. It has been observed that many Open Source projects follow agile practices of parallel development and Rapid Releases (RR) but, very few studies till date, have analyzed release patterns of these Open Source projects. This paper analyzes ten Open Source Java projects (Apache Server Foundation) comprising 718 releases to study the evolution of release lengths. The results of the study show that: (1) eight out of ten datasets followed RR models. (2) None of these datasets followed RR models since their first release. (3) The average release length was found to be four months for major versions and one month for minor versions (exceptions removed). (4) There exists a negative correlation between number of contributors and release length. © 2019, Springer Nature Singapore Pte Ltd.},
  key = {Kaur20199},
  pages = {9-18},
  journal = {Advances in Intelligent Systems and Computing},
  volume = {711},
  note = {cited By 0}
}

@inproceedings{teixeira2017a,
  title = {Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management},
  author = {Teixeira, Jose},
  year = {2017},
  url = {http://doi.org/10.1007/978-3-319-57735-7_16},
  abstract = {The dictum of ``Release early, release often.'' by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. Nevertheless, there are very few empirical studies addressing release management in open source software development. It is already known that most open source software communities adopt either feature-based or time-based release strategies. Each of these has its advantages and disadvantages that are context-specific. Recent research reported that many prominent open source software projects have moved from feature-based to time-based releases. In this longitudinal case study, we narrate how OpenStack shifted towards a liberal six-month release cycle. If prior research discussed why projects should adopt time-based releases and how they can adopt such a strategy, we discuss how OpenStack adapted its software development processes, its organizational design and its tools toward a hybrid release management strategy --- a strive for balancing the benefits and drawbacks of feature-based and time-based release strategies.},
  doi = {10.1007/978-3-319-57735-7_16},
  editors = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Robles, Gregorio and Zacchiroli, Stefano},
  booktitle = {Open Source Systems: Towards Robust Practices},
  publisher = {Springer International Publishing},
  address = {Cham},
  pages = {167--181},
  note = {Paper extracted manually from book at URL.}
}

@phdthesis{poo-caama2016a,
  title = {Release management in free and open source software ecosystems},
  author = {Poo-Caama{\~n}o, Germ{\'a}n},
  year = {2016},
  url = {http://dspace.library.uvic.ca/handle/1828/7648},
  key = {poo2016release}
}

@article{mantyla2015a,
  title = {On rapid releases and software testing: a case study and a semi-systematic literature review},
  author = {M{\"a}ntyl{\"a}, Mika V. and Adams, Bram and Khomh, Foutse and Engstr{\"o}m, Emelie and Petersen, Kai},
  year = {2015},
  url = {https://doi.org/10.1007/s10664-014-9338-4},
  abstract = {Large open and closed source organizations like Google, Facebook and Mozilla are migrating their products towards rapid releases. While this allows faster time-to-market and user feedback, it also implies less time for testing and bug fixing. Since initial research results indeed show that rapid releases fix proportionally less reported bugs than traditional releases, this paper investigates the changes in software testing effort after moving to rapid releases in the context of a case study on Mozilla Firefox, and performs a semi-systematic literature review. The case study analyzes the results of 312,502 execution runs of the 1,547 mostly manual system-level test cases of Mozilla Firefox from 2006 to 2012 (5 major traditional and 9 major rapid releases), and triangulates our findings with a Mozilla QA engineer. We find that rapid releases have a narrower test scope that enables a deeper investigation of the features and regressions with the highest risk. Furthermore, rapid releases make testing more continuous and have proportionally smaller spikes before the main release. However, rapid releases make it more difficult to build a large testing community , and they decrease test suite diversity and make testing more deadline oriented. In addition, our semi-systematic literature review presents the benefits, problems and enablers of rapid releases from 24 papers found using systematic search queries and a similar amount of papers found through other means. The literature review shows that rapid releases are a prevalent industrial practice that are utilized even in some highly critical domains of software engineering, and that rapid releases originated from several software development methodologies such as agile, open source, lean and internet-speed software development. However, empirical studies proving evidence of the claimed advantages and disadvantages of rapid releases are scarce.},
  key = {Mäntylä2015},
  pages = {1384--1425},
  journal = {Empirical Software Engineering},
  number = {5},
  volume = {20},
  note = {Had found "https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=\&arnumber=7006390", this paper is second reference on page 2}
}
@inproceedings{plewnia2014a,
  title = {On the influence of release engineering on software reputation},
  author = {Plewnia, Christian and Dyck, Andrej and Lichter, Horst},
  year = {2014},
  key = {plewnia2014influence},
  booktitle = {Mountain View, CA, USA: In 2nd International Workshop on Release Engineering},
  note = {Had found "https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=\&arnumber=7006390", this paper is first reference on page 2}
}
@article{khomh2015a,
  title = {Understanding the impact of rapid releases on software quality},
  author = {Khomh, Foutse and Adams, Bram and Dhaliwal, Tejinder and Zou, Ying},
  year = {2015},
  url = {https://doi.org/10.1007/s10664-014-9308-x},
  abstract = {Many software companies are shifting from the traditional multi-month release cycle to shorter release cycles. For example, Google Chrome and Mozilla Firefox release new versions every 6 weeks. These shorter release cycles reduce the users' waiting time for a new release and offer better feedback and marketing opportunities to companies, but it is unclear if the quality of the software product improves as well, since developers and testers are under more pressure. In this paper, we extend our previous empirical study of Mozilla Firefox on the impact of rapid releases on quality assurance with feedback by Mozilla project members. The study compares crash rates, median uptime, and the proportion of pre- and post-release bugs in traditional releases with those in rapid releases, and we also analyze the source code changes made by developers to identify potential changes in the development process. We found that (1) with shorter release cycles, users do not experience significantly more pre- or post-release bugs (percentage-wise) and (2) bugs are fixed faster, yet (3) users experience these bugs earlier during software execution (the program crashes earlier). Increased integration activity and propagation of harder bugs to later versions account for some of these findings. Overall, our case study suggests that a clear release engineering process with thorough automation is one of the major challenges when switching to rapid releases.},
  key = {Khomh2015},
  pages = {336--373},
  journal = {Empirical Software Engineering},
  number = {2},
  volume = {20}
}
@inproceedings{khomh2012a,
  title = {Do Faster Releases Improve Software Quality?: An Empirical Case Study of Mozilla Firefox},
  author = {Khomh, Foutse and Dhaliwal, Tejinder and Zou, Ying and Adams, Bram},
  year = {2012},
  url = {http://dl.acm.org/citation.cfm?id=2664446.2664475},
  keywords = {bugs, release cycle, software quality, software release, testing},
  key = {Khomh:2012:FRI:2664446.2664475},
  booktitle = {Proceedings of the 9th IEEE Working Conference on Mining Software Repositories},
  publisher = {IEEE Press},
  address = {Piscataway, NJ, USA},
  series = {MSR '12},
  pages = {179--188}
}
@inproceedings{d2014a,
  title = {An Empirical Study of Delays in the Integration of Addressed Issues},
  author = {d. Costa, D. A. and Abebe, S. L. and Mcintosh, S. and Kulesza, U. and Hassan, A. E.},
  year = {2014},
  url = {https://doi.org/10.1109/ICSME.2014.50},
  keywords = {sensitivity analysis;software engineering;empirical analysis;software engineering;addressed issue integration;ArgoUML project;Eclipse project;Firefox project;release cycle;ROC area;receiver operator curve area;integrator workload;influential factor;integration delay models;nonnegligible delays;software system;Delays;Databases;Software;Unified modeling language;Educational institutions;Receivers},
  key = {6976094},
  booktitle = {2014 IEEE International Conference on Software Maintenance and Evolution},
  pages = {281-290}
}
@inproceedings{da2016a,
  title = {The Impact of Switching to a Rapid Release Cycle on the Integration Delay of Addressed Issues - An Empirical Study of the Mozilla Firefox Project},
  author = {da Costa, D. A. and McIntosh, S. and Kulesza, U. and Hassan, A. E.},
  year = {2016},
  url = {https://doi.org/10.1109/MSR.2016.045},
  keywords = {project management;software development management;software projects release frequency;code integration phase;integration delay;Mozilla Firefox Project;rapid release cycle;Computer bugs;Software;Delays;Marine vehicles;History;Context;Delivery delay;Release engineering;Empirical study},
  key = {7832916},
  booktitle = {2016 IEEE/ACM 13th Working Conference on Mining Software Repositories (MSR)},
  pages = {374-385}
}
@inproceedings{adams2016a,
  title = {Modern release engineering in a nutshell--why researchers should care},
  author = {Adams, Bram and McIntosh, Shane},
  year = {2016},
  url = {https://doi.org/10.1109/SANER.2016.108},
  key = {adams2016modern},
  booktitle = {Software Analysis, Evolution, and Reengineering (SANER), 2016 IEEE 23rd International Conference on},
  organization = {IEEE},
  pages = {78--90},
  volume = {5}
}

@inproceedings{bavota2015four,
  title={Four eyes are better than two: On the impact of code reviews on software quality},
  author={Bavota, Gabriele and Russo, Barbara},
  booktitle={Software Maintenance and Evolution (ICSME), 2015 IEEE International Conference on},
  pages={81--90},
  year={2015},
  organization={IEEE}
}

@inproceedings{KKK2016,
  title={Static program analysis for identifying energy bugs in graphics-intensive mobile apps},
  author={Kim, Chang Hwan Peter and Kroening, Daniel and Kwiatkowska, Marta},
  booktitle={Modeling, Analysis and Simulation of Computer and Telecommunication Systems (MASCOTS), 2016 IEEE 24th International Symposium on},
  pages={115--124},
  year={2016},
  organization={IEEE}
}

@inproceedings{BAW2017,
  title={Deep parameter optimisation on Android smartphones for energy minimisation: a tale of woe and a proof-of-concept},
  author={Bokhari, Mahmoud A and Bruce, Bobby R and Alexander, Brad and Wagner, Markus},
  booktitle={Proceedings of the Genetic and Evolutionary Computation Conference Companion},
  pages={1501--1508},
  year={2017},
  organization={ACM}
}

@article{MPF2017,
  title={An empirical study of the power consumption of cryptographic primitives in Android},
  author={Montenegro, Jose A and Pinto, Monica and Fuentes, Lidia},
  journal={arXiv preprint arXiv:1705.03558},
  year={2017}
}

@article{MPF2018,
  title={What do software developers need to know to build secure energy-efficient Android applications?},
  author={Montenegro, Jos{\'e} A and Pinto, M{\'o}nica and Fuentes, Lidia},
  journal={IEEE ACCESS},
  volume={6},
  pages={1428--1450},
  year={2018},
  publisher={IEEE-INST ELECTRICAL ELECTRONICS ENGINEERS INC 445 HOES LANE, PISCATAWAY, NJ 08855-4141 USA}
}

@inproceedings{BSB2017,
  title={A Methodology for Relating Software Structure with Energy Consumption},
  author={Bangash, Abdul Ali and Sahar, Hareem and Beg, Mirza Omer},
  booktitle={Source Code Analysis and Manipulation (SCAM), 2017 IEEE 17th International Working Conference on},
  pages={111--120},
  year={2017},
  organization={IEEE}
}

@inproceedings{LWXM2017,
  title={NavyDroid: Detecting energy inefficiency problems for smartphone applications},
  author={Liu, Yi and Wang, Jue and Xu, Chang and Ma, Xiaoxing},
  booktitle={Proceedings of the 9th Asia-Pacific Symposium on Internetware},
  pages={8},
  year={2017},
  organization={ACM}
}

@article{CA2018,
  title={Using Automatic Refactoring to Improve Energy Efficiency of Android Apps},
  author={Cruz, Luis and Abreu, Rui},
  journal={arXiv preprint arXiv:1803.05889},
  year={2018}
}

@inproceedings{GMNH2015,
  title={Truth in advertising: The hidden cost of mobile ads for software developers},
  author={Gui, Jiaping and Mcilroy, Stuart and Nagappan, Meiyappan and Halfond, William GJ},
  booktitle={Proceedings of the 37th International Conference on Software Engineering-Volume 1},
  pages={100--110},
  year={2015},
  organization={IEEE Press}
}

@inproceedings{LHG2014,
  title={An empirical study of the energy consumption of android applications},
  author={Li, Ding and Hao, Shuai and Gui, Jiaping and Halfond, William GJ},
  booktitle={Software Maintenance and Evolution (ICSME), 2014 IEEE International Conference on},
  pages={121--130},
  year={2014},
  organization={IEEE}
}

@inproceedings{MPEC2015,
  title={Mining energy-aware commits},
  author={Moura, Irineu and Pinto, Gustavo and Ebert, Felipe and Castor, Fernando},
  booktitle={Proceedings of the 12th Working Conference on Mining Software Repositories},
  pages={56--67},
  year={2015},
  organization={IEEE Press}
}

@inproceedings{BLXWT2016,
  title={How android app developers manage power consumption?: An empirical study by mining power management commits},
  author={Bao, Lingfeng and Lo, David and Xia, Xin and Wang, Xinyu and Tian, Cong},
  booktitle={Proceedings of the 13th International Conference on Mining Software Repositories},
  pages={37--48},
  year={2016},
  organization={ACM}
}

@inproceedings{LHHG2013,
  title={Calculating source line level energy information for android applications},
  author={Li, Ding and Hao, Shuai and Halfond, William GJ and Govindan, Ramesh},
  booktitle={Proceedings of the 2013 International Symposium on Software Testing and Analysis},
  pages={78--89},
  year={2013},
  organization={ACM}
}

@inproceedings{WLXML2016,
  title={E-greenDroid: effective energy inefficiency analysis for android applications},
  author={Wang, Jue and Liu, Yepang and Xu, Chang and Ma, Xiaoxing and Lu, Jian},
  booktitle={Proceedings of the 8th Asia-Pacific Symposium on Internetware},
  pages={71--80},
  year={2016},
  organization={ACM}
}

@inproceedings{LLGH2016,
  title={Automated energy optimization of http requests for mobile applications},
  author={Li, Ding and Lyu, Yingjun and Gui, Jiaping and Halfond, William GJ},
  booktitle={Proceedings of the 38th international conference on software engineering},
  pages={249--260},
  year={2016},
  organization={ACM}
}

@inproceedings{PCL2014,
  title={Mining questions about software energy consumption},
  author={Pinto, Gustavo and Castor, Fernando and Liu, Yu David},
  booktitle={Proceedings of the 11th Working Conference on Mining Software Repositories},
  pages={22--31},
  year={2014},
  organization={ACM}
}

@inproceedings{kononenko2015investigating,
  title={Investigating code review quality: Do people and participation matter?},
  author={Kononenko, Oleksii and Baysal, Olga and Guerrouj, Latifa and Cao, Yaxin and Godfrey, Michael W},
  booktitle={Software Maintenance and Evolution (ICSME), 2015 IEEE International Conference on},
  pages={111--120},
  year={2015},
  organization={IEEE}
}

@inproceedings{bernhart2012applying,
  title={Applying continuous code reviews in airport operations software},
  author={Bernhart, Mario and Strobl, Stefan and Mauczka, Andreas and Grechenig, Thomas},
  booktitle={Quality Software (QSIC), 2012 12th International Conference on},
  pages={214--219},
  year={2012},
  organization={IEEE}
}

@inproceedings{shimagaki2016study,
  title={A study of the quality-impacting practices of modern code review at sony mobile},
  author={Shimagaki, Junji and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E and Ubayashi, Naoyasu},
  booktitle={Software Engineering Companion (ICSE-C), IEEE/ACM International Conference on},
  pages={212--221},
  year={2016},
  organization={IEEE}
}

@inproceedings{yang2016mining,
  title={Mining the modern code review repositories: A dataset of people, process and product},
  author={Yang, Xin and Kula, Raula Gaikovina and Yoshida, Norihiro and Iida, Hajimu},
  booktitle={Proceedings of the 13th International Conference on Mining Software Repositories},
  pages={460--463},
  year={2016},
  organization={ACM}
}