References - nsalminen/software-analytics-book GitHub Wiki

@adams2016a: Adams, Bram, and Shane McIntosh. 2016. “Modern Release Engineering in a Nutshell–Why Researchers Should Care.” In Software Analysis, Evolution, and Reengineering (Saner), 2016 Ieee 23rd International Conference on, 5:78–90. IEEE. https://doi.org/10.1109/SANER.2016.108.
@castelluccio2017a: Castelluccio, M., L. An, and F. Khomh. 2017. “Is It Safe to Uplift This Patch? An Empirical Study on Mozilla Firefox.” In Proceedings - 2017 IEEE International Conference on Software Maintenance and Evolution, ICSME 2017, 411–21. https://www.scopus.com/inward/record.uri?eid=2-s2.0-85040634374&doi=10.1109%2fICSME.2017.82&partnerID=40&md5=db36b40c2534743b53a2379157b50a59.
@claes2017a: Claes, M., M. Mantyla, M. Kuutila, and B. Adams. 2017. “Abnormal Working Hours: Effect of Rapid Releases and Implications to Work Content.” In IEEE International Working Conference on Mining Software Repositories, 243–47. https://www.scopus.com/inward/record.uri?eid=2-s2.0-85026506528&doi=10.1109%2fMSR.2017.3&partnerID=40&md5=2da8fa8a15b9ffb4b1969663af15ecac.
@da2014a: Costa, D. A. da, S. L. Abebe, S. Mcintosh, U. Kulesza, and A. E. Hassan. 2014. “An Empirical Study of Delays in the Integration of Addressed Issues.” In 2014 Ieee International Conference on Software Maintenance and Evolution, 281–90. https://doi.org/10.1109/ICSME.2014.50.
@da2016a: Costa, D. A. da, S. McIntosh, U. Kulesza, and A. E. Hassan. 2016. “The Impact of Switching to a Rapid Release Cycle on the Integration Delay of Addressed Issues - an Empirical Study of the Mozilla Firefox Project.” In 2016 Ieee/Acm 13th Working Conference on Mining Software Repositories (Msr), 374–85. https://doi.org/10.1109/MSR.2016.045.
@dyck2015a: Dyck, Andrej, Ralf Penners, and Horst Lichter. 2015. “Towards Definitions for Release Engineering and Devops.” In Release Engineering (Releng), 2015 Ieee/Acm 3rd International Workshop on, 3–3. IEEE. https://www2.swc.rwth-aachen.de/docs/RELENG2015/DevOpsVsRelEng.pdf.
@fujibayashi2017a: Fujibayashi, D., A. Ihara, H. Suwa, R.G. Kula, and K. Matsumoto. 2017. “Does the Release Cycle of a Library Project Influence When It Is Adopted by a Client Project?” In SANER 2017 - 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering, 569–70. https://www.scopus.com/inward/record.uri?eid=2-s2.0-85018384049&doi=10.1109%2fSANER.2017.7884681&partnerID=40&md5=83955b8bec9726f3eb1bc751b3c5f2f8.
@karvonen2017a: Karvonen, T., W. Behutiye, M. Oivo, and P. Kuvaja. 2017. “Systematic Literature Review on the Impacts of Agile Release Engineering Practices.” Information and Software Technology 86: 87–100. https://www.scopus.com/inward/record.uri?eid=2-s2.0-85028272067&doi=10.1016%2fj.infsof.2017.01.009&partnerID=40&md5=001c120eea2481c21dae5a551b44dd39.
@khomh2012a: Khomh, Foutse, Tejinder Dhaliwal, Ying Zou, and Bram Adams. 2012. “Do Faster Releases Improve Software Quality?: An Empirical Case Study of Mozilla Firefox.” In Proceedings of the 9th Ieee Working Conference on Mining Software Repositories, 179–88. MSR ’12. Piscataway, NJ, USA: IEEE Press. http://dl.acm.org/citation.cfm?id=2664446.2664475.
@khomh2015a: Khomh, Foutse, Bram Adams, Tejinder Dhaliwal, and Ying Zou. 2015. “Understanding the Impact of Rapid Releases on Software Quality.” Empirical Software Engineering 20 (2): 336–73. https://doi.org/10.1007/s10664-014-9308-x.
@kitchenham2004procedures: Kitchenham, Barbara. 2004b. “Procedures for Performing Systematic Reviews.” Keele, UK, Keele University 33 (2004): 1–26.
@laukkanen2017a: Laukkanen, Eero, Juha Itkonen, and Casper Lassenius. 2017. “Problems, Causes and Solutions When Adopting Continuous Delivery—a Systematic Literature Review.” Information and Software Technology 82. Elsevier: 55–79.
@laukkanen2018a: Laukkanen, E., M. Paasivaara, J. Itkonen, and C. Lassenius. 2018. “Comparison of Release Engineering Practices in a Large Mature Company and a Startup.” Empirical Software Engineering, 1–43. https://www.scopus.com/inward/record.uri?eid=2-s2.0-85044460784&doi=10.1007%2fs10664-018-9616-7&partnerID=40&md5=dcca7b080050cb81ac889e6eede2b3cc.
@mantyla2015a: Mäntylä, Mika V., Bram Adams, Foutse Khomh, Emelie Engström, and Kai Petersen. 2015. “On Rapid Releases and Software Testing: A Case Study and a Semi-Systematic Literature Review.” Empirical Software Engineering 20 (5): 1384–1425. https://doi.org/10.1007/s10664-014-9338-4.
@poo-caamano2016a: Poo-Caamaño, Germán. 2016. “Release Management in Free and Open Source Software Ecosystems.” PhD thesis. http://dspace.library.uvic.ca/handle/1828/7648.
@rodriguez2017a: Rodríguez, Pilar, Alireza Haghighatkhah, Lucy Ellen Lwakatare, Susanna Teppola, Tanja Suomalainen, Juho Eskeli, Teemu Karvonen, Pasi Kuvaja, June M Verner, and Markku Oivo. 2017. “Continuous Deployment of Software Intensive Products and Services: A Systematic Mapping Study.” Journal of Systems and Software 123. Elsevier: 263–91.
@souza2015a: Souza, R., C. Chavez, and R.A. Bittencourt. 2015. “Rapid Releases and Patch Backouts: A Software Analytics Approach.” IEEE Software 32 (2): 89–96. https://www.scopus.com/inward/record.uri?eid=2-s2.0-84925218343&doi=10.1109%2fMS.2015.30&partnerID=40&md5=d624ac5b06a61704543a6d72af3981a1.
@teixeira2017a: Teixeira, Jose. 2017. “Release Early, Release Often and Release on Time. an Empirical Case Study of Release Management.” In Open Source Systems: Towards Robust Practices, 167–81. Cham: Springer International Publishing. doi:10.1007/978-3-319-57735-7_16.