Modern release engineering in a nutshell: Why researchers should care

2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering, SANER 2016

Volumn 2016-January, Issue , 2016, Pages 78-90

  Adams, Bram ^a   McIntosh, Shane ^b  

^a ÉCOLE POLYTECHNIQUE DE MONTRÉAL   (Canada)

^b MCGILL UNIVERSITY   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SOFTWARE SELECTION AND EVALUATION; PIPELINES; REENGINEERING; SPECIFICATIONS;

BEST PRACTICES; BUILD SYSTEMS; CODE CHANGES; CONTINUOUS INTEGRATIONS; EMPIRICAL VALIDATION; ENGINEERING PROCESS; HIGH QUALITY; RESEARCH OPPORTUNITIES;

SOFTWARE QUALITY;

EID: 84974531462     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SANER.2016.108     Document Type: Conference Paper

References (91)

1. B. Adams, S. Bellomo, C. Bird, F. Khomh, and K. Moir, “Intl. workshop on release engineering (RELENG),” http://releng.polymtl.ca.
2. B. Adams, S. Bellomo, C. Bird, T. Marshall-Keim, F. Khomh, and K. Moir, “The practice and future of release engineering - a roundtable with three release engineers,” IEEE Software, vol. 32, no. 2, pp. 42-49, 2015.
3. B. Adams, K. De Schutter, H. Tromp, and W. De Meuter, “The evolution of the linux build system,” Electronic Communications of the ECEASST, vol. 8, February 2008.
4. B. Adams, K. De Schutter, H. Tromp, and W. D. Meuter, “Design recovery and maintenance of build systems,” in Proc. of the Intl. Conf. on Soft. Maint., 2007, pp. 114-123.
5. B. Adams, R. Kavanagh, A. E. Hassan, and D. M. German, “An empirical study of integration activities in distributions of open source software,” Empirical Software Engineering, 2015, to appear.
6. R. Aiello and L. Sachs, Configuration Management Best Practices: Practical Methods That Work in the Real World, 1st ed. Addison-Wesley Professional, 2010.
7. J. M. Al-Kofahi, H. V. Nguyen, A. T. Nguyen, T. T. Nguyen, and T. N. Nguyen, “Detecting semantic changes in makefile build code,” in Proc. of the Intl. Conf. on Software Maintenance (ICSM), 2012, pp. 150-159.
8. A. Bacchelli and C. Bird, “Expectations, outcomes, and challenges of modern code review,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2013, pp. 712-721.
9. L. Bass, I. Weber, and L. Zhu, DevOps: A Software Architect's Perspective, 1st ed., ser. SEI Series in Software Engineering. Addison-Wesley Professional, May 2015.
10. O. Baysal, I. Davis, and M. W. Godfrey, “A tale of two browsers,” in Proc. of the 8th Working Conf. on Mining Software Repositories (MSR), 2011, pp. 238-241.
11. O. Baysal, O. Kononenko, R. Holmes, and M. W. Godfrey, “The influence of non-technical factors on code review,” in Proc. of the Working Conf. on Reverse Engineering (WCRE), 2013, pp. 122-131.
12. M. Beller, A. Bacchelli, A. Zaidman, and E. Juergens, “Modern code reviews in open-source projects: Which problems do they fix?” in Proc. of the Working Conf. on Mining Software Repositories (MSR), 2014, pp. 202-211.
13. S. P. Berczuk and B. Appleton, Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Addison-Wesley Longman Publishing Co., Inc., 2002.
14. R. Bernstein, “Debugging makefiles with remake,” in Proc. of the 25th Intl. Conf. on Large Installation System Administration (LISA), 2011, pp. 27-27.
15. N. Bettenburg, A. E. Hassan, B. Adams, and D. M. German, “Management of community contributions: A case study on the android and Linux software ecosystems,” Empirical Software Engineering, vol. 20, no. 1, pp. 252-289, February 2015.
16. C. Bird, P. C. Rigby, E. T. Barr, D. J. Hamilton, D. M. German, and P. Devanbu, “The promises and perils of mining git,” in Proc. of the 2009 6th IEEE Intl. Working Conf. on Mining Software Repositories (MSR), 2009, pp. 1-10.
17. C. Bird and T. Zimmermann, “Assessing the value of branches with what-if analysis,” in Proc. of the Intl. Symp. on Foundations of Software Engineering (FSE), 2012.
18. Y. Brun, R. Holmes, M. D. Ernst, and D. Notkin, “Proactive detection of collaboration conflicts,” in Proc. of the 19th ACM SIGSOFT Symp. and the 13th European Conf. on Foundations of Software Engineering (ESEC/FSE), 2011, pp. 168-178.
19. S. Chacon, Pro Git, 1st ed. Berkely, CA, USA: Apress, 2009.
20. H. Dayani-Fard, Y. Yu, J. Mylopoulos, and P. Andritsos, “Improving the build architecture of legacy c/c++ software systems,” in Proc. of the 8th Intl. Conf., Held As Part of the Joint European Conf. on Theory and Practice of Software Conf. on Fundamental Approaches to Software Engineering (FASE), 2005, pp. 96-110.
21. M. de Jonge, “Build-level components,” IEEE Trans. Softw. Eng., vol. 31, no. 7, pp. 588-600, Jul. 2005.
22. A. Dearle, “Software deployment, past, present and future,” in 2007 Future of Software Engineering (FOSE), 2007, pp. 269-284.
23. I. Docker, “Docker,” https://www.docker.com.
24. E. Dolstra, M. de Jonge, and E. Visser, “Nix: A safe and policy-free system for software deployment,” in Proc. of the 18th USENIX conf. on System admin., 2004, pp. 79-92.
25. P. Duvall, S. M. Matyas, and A. Glover, Continuous Integration: Improving Software Quality and Reducing Risk. Addison-Wesley Professional, 2007.
26. T. Fitz, “Continuous deployment at IMVU: Doing the impossible fifty times a day,” http://timothyfitz.com/2009/02/10/continuous-deploymentat-imvu-doing-the-impossible-fifty-times-a-day/, February 2009.
27. D. M. German, B. Adams, and A. E. Hassan, “Continuously mining the use of distributed version control systems: An empirical study of how linux uses git,” Empirical Software Engineering, 2015, to appear.
28. “Gitian,” https://gitian.org.
29. M. Gómez, M. Martinez, M. Monperrus, and R. Rouvoy, “When app stores listen to the crowd to fight bugs in the wild,” in Proc. of the 37th Intl. Conf. on Software Engineering (ICSE) - Volume 2, 2015, pp. 567-570.
30. G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work practices and challenges in pull-based development: The integrator's perspective,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2015, pp. 358-368.
31. J. Graham-Cumming, “Gnu make debugger,” http://gmd.sourceforge.net, 2014.
32. M. L. Guimarães and A. R. Silva, “Improving early detection of software merge conflicts,” in Proc. of the 34th Intl. Conf. on Software Engineering (ICSE), 2012, pp. 342-352.
33. R. Hardt and E. V. Munson, “An empirical evaluation of ant build maintenance using formiga,” in Proc. of the Intl. Conf. on Software Maintenance and Evolution, 2015, pp. 201-210.
34. A. E. Hassan and K. Zhang, “Using decision trees to predict the certification result of a build,” in Proc. of the 21st IEEE/ACM Intl. Conf. on Automated Software Engineering (ASE), 2006, pp. 189-198.
35. K. Herzig, M. Greiler, J. Czerwonka, and B. Murphy, “The art of testing less without sacrificing quality,” in Proc. of the 37th Intl. Conf. on Software Engineering (ICSE) - Volume 1, 2015, pp. 483-493.
36. J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, 1st ed. Addison-Wesley Professional, 2010.
37. Y. Jiang and B. Adams, “Co-evolution of infrastructure and source code: An empirical study,” in Proc. of the 12th Working Conf. on Mining Software Repositories (MSR), 2015, pp. 45-55.
38. Y. Jiang, B. Adams, and D. M. German, “Will my patch make it? and how fast? - case study on the linux kernel,” in Proc. of the 10th IEEE Working Conf. on Mining Software Repositories (MSR), 2013, pp. 101-110.
39. C. F. Kemerer and M. C. Paulk, “The impact of design and code reviews on software quality: An empirical study based on psp data,” Transactions on Software Engineering (TSE), vol. 35, no. 4, pp. 534-550, April 2009.
40. N. Kerzazi and B. Adams, “Botched releases: Do we need to roll back? empirical study on a commercial web app,” in Proc. of the 23rd IEEE Intl. Conf. on Software Analysis, Evolution, and Reengineering (SANER), Osaka, Japan, March 2016.
41. N. Kerzazi, F. Khomh, and B. Adams, “Why do automated builds break? an empirical study,” in Proc. of the 30th IEEE Intl. Conf. on Software Maintenance (ICSM), 2014, pp. 41-50.
42. H. Khalid, E. Shihab, M. Nagappan, and A. Hassan, “What do mobile app users complain about?” Software, IEEE, vol. 32, no. 3, pp. 70-77, May 2015.
43. F. Khomh, T. Dhaliwal, Y. Zou, and B. Adams, “Do faster releases improve software quality? an empirical case study of mozilla firefox,” in Proc. of the Working Conf. on Mining Software Repositories (MSR), 2012, pp. 179-188.
44. O. Kononenko, O. Baysal, L. Guerrouj, Y. Cao, and M. W. Godfrey, “Investigating code review quality: Do people and participation matter?” in Proc. of the Intl. Conf. on Software Maintenance and Evolution (ICSME), 2015, pp. 111-120.
45. M. Mäntylä, F. Khomh, B. Adams, E. Engström, and K. Petersen, “On rapid releases and software testing,” in Proc. of the 29th IEEE Intl. Conf. on Software Maintenance (ICSM), 2013, pp. 20-29.
46. M. V. Mäntylä and C. Lassenius, “What types of defects are really discovered in code reviews?” Transactions on Software Engineering (TSE), vol. 35, no. 3, pp. 430-448, June 2009.
47. S. McIntosh, B. Adams, M. Nagappan, and A. E. Hassan, “Identifying and understanding header file hotspots in c/c++ build processes,” Automated Software Engineering, 2015, to appear.
48. S. McIntosh, B. Adams, T. H. Nguyen, Y. Kamei, and A. E. Hassan, “An empirical study of build maintenance effort,” in Proc. of the 33rd Intl. Conf. on Software Engineering (ICSE), 2011, pp. 141-150.
49. S. McIntosh, Y. Kamei, B. Adams, and A. E. Hassan, “An empirical study of the impact of modern code review practices on software quality,” Empirical Software Engineering, vol. In press, 2015.
50. S. McIntosh, M. Nagappan, B. Adams, A. Mockus, and A. E. Hassan, “A large-scale empirical study of the relationship between build technology and build maintenance,” Empirical Software Engineering, vol. In press, 2015.
51. A. Meneely, A. C. R. Tejeda, B. Spates, S. Trudeau, D. Neuberger, K. Whitlock, C. Ketant, and K. Davis, “An empirical investigation of socio-technical code review metrics and security vulnerabilities,” in Proc. of the Intl. Workshop on Social Software Engineering (SSE), 2014, pp. 37-44.
52. R. Morales, S. McIntosh, and F. Khomh, “Do code review practices impact design quality? a case study of the qt, vtk, and itk projects,” in Proc. of the Intl. Conf. on Software Analysis, Evolution, and Reengineering (SANER), 2015, pp. 171-180.
53. S. Nadi, T. Berger, C. Kästner, and K. Czarnecki, “Mining configuration constraints: Static analyses and empirical results,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2014, pp. 140-151.
54. S. Nadi, C. Dietrich, R. Tartler, R. C. Holt, and D. Lohmann, “Linux variability anomalies: What causes them and how do they get fixed?” in Proc. of the Working Conf. on Mining Software Repositories (MSR), 2013, pp. 111-120.
55. M. Nayebi, B. Adams, and G. Ruhe, “Release practices in mobile apps - users and developers perception,” in Proc. of the 23rd IEEE Intl. Conf. on Software Analysis, Evolution, and Reengineering (SANER), 2016.
56. A. project, “Antelope,” http://antelope.stage.tigris.org, 2009.
57. S. Raemaekers, A. van Deursen, and J. Visser, “Measuring software library stability through historical version analysis,” in Proc. of the 28th IEEE Intl. Conf. on Software Maintenance (ICSM), 2012, pp. 378-387.
58. S. Raemaekers, A. van Deursen, and J. Visser, “Semantic versioning versus breaking changes: a study of the maven repository,” in Proc. of the 14th Intl. Working Conf. on Source Code Analysis and Manipulation (SCAM), 2014, pp. 215-224.
59. A. Rahman, E. Helms, L. Williams, and C. Parnin, “Synthesizing continuous deployment practices used in software development,” in Proc. of the 2015 Agile Conf. (AGILE), 2015, pp. 1-10.
60. M. Rahman and P. Rigby, “Release stabilization on linux and chrome,” Software, IEEE, vol. 32, no. 2, pp. 81-88, Mar 2015.
61. “Provide a verifiable path from source code to binary,” https://reproducible-builds.org.
62. P. C. Rigby, D. M. German, and M.-A. Storey, “Open source software peer review practices: A case study of the apache server,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2008, pp. 541-550.
63. P. C. Rigby and M.-A. Storey, “Understanding broadcast based peer review on open source software projects,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2011, pp. 541-550.
64. P. Rodríguez, A. Haghighatkhah, L. E. Lwakatare, S. Teppola, T. Suomalainen, J. Eskeli, T. Karvonen, P. Kuvaja, J. M. Verner, and M. Oivo, “Continuous deployment of software intensive products and services: A systematic mapping study,” Journal of Systems and Software (JSS), 2016, to appear.
65. C. Rossi, “Moving to mobile: The challenges of moving from web to mobile releases,” Keynote at RELENG 2014, April 2014, https://www.youtube.com/watch?v=Nffzkkdq7GM.
66. A. Sarma, Z. Noroozi, and A. van der Hoek, “Palantir: raising awareness among configuration management workspaces,” in Proc. of the 25th Intl. Conf. on Software Engineering (ICSE), 2003, pp. 444-454.
67. S. Schoen and M. Perry, “Why and how of reproducible builds: Distrusting our own infrastructure for safer software releases,” https://air.mozilla.org/why-and-how-of-reproducible-builds-distrusting-our-own-infrastructure\-for-safer-software-releases/, November 2014.
68. H. Seo, C. Sadowski, S. Elbaum, E. Aftandilian, and R. Bowdidge, “Programmers' build errors: A case study (at google),” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2014, pp. 724-734.
69. S. Shankland, “Google ethos speeds up chrome release cycle,” http://cnet.co/wlS24U, July 2010.
70. S. Shankland, “Rapid-release firefox meets corporate backlash,” http://cnet.co/ktBsUU, June 2011.
71. E. Shihab, C. Bird, and T. Zimmermann, “The effect of branching strategies on software quality,” in Proc. of the Intl. Symp. on Empirical Software Engineering and Measurement (ESEM), 2012, pp. 301-310.
72. M. Shridhar, B. Adams, and F. Khomh, “A qualitative analysis of software build system changes and build ownership styles,” in Proc. of the 8th Intl. Symp. on Empirical Software Engineering and Measurement (ESEM), 2014.
73. D. Ståhl and J. Bosch, “Modeling continuous integration practice differences in industry software development,” J. Syst. Softw., vol. 87, pp. 48-59, Jan. 2014.
74. Statista, “Cumulative number of apps downloaded from the apple app store from july 2008 to june 2015 (in billions),” http://www.statista.com/statistics/263794/number-of-downloads-fromthe-apple-app-store/, June 2015.
75. Statista, “Number of apps available in leading app stores as of july 2015,” http://www.statista.com/statistics/276623/number-of-appsavailable-in-leading-app-stores/, July 2015.
76. N. Sussman, “Continuous delivery is mainstream,” http://infiniteundo.com/post/71540519157/continuous-delivery-is-mainstream, 2014.
77. R. Suvorov, B. Adams, M. Nagappan, A. Hassan, and Y. Zou, “An empirical study of build system migrations in practice: Case studies on kde and the linux kernel,” in Proc. of the 28th IEEE Intl. Conf. on Software Maintenance (ICSM), 2012, pp. 160-169.
78. P. Systems, “Virtual ant,” http://www.placidsystems.com/virtualant/, 2007.
79. A. Tamrawi, H. A. Nguyen, H. V. Nguyen, and T. N. Nguyen, “Build code analysis with symbolic evaluation,” in Proc. of the Intl. Conf. on Software Engineering (ICSE), 2012, pp. 650-660.
80. A. S. Tanenbaum and H. Bos, Modern Operating Systems, 4th ed. Prentice Hall Press, 2014.
81. P. Thongtanunam, S. McIntosh, A. E. Hassan, and H. Iida, “Investigating code review practices in defective files: An empirical study of the qt system,” in Proc. of the Working Conf. on Mining Software Repositories (MSR), 2015, pp. 168-179.
82. “Mozilla try server,” https://wiki.mozilla.org/ReleaseEngineering/TryServer.
83. Q. Tu and M. W. Godfrey, “The build-time software architecture view,” in Proc. of the IEEE Intl. Conf. on Software Maintenance (ICSM), 2001, pp. 398-407.
84. M. Vakilian, R. Sauciuc, J. D. Morgenthaler, and V. Mirrokni, “Automated decomposition of build targets,” in Proc. of the 37th Intl. Conf. on Software Engineering (ICSE) - Volume 1, 2015, pp. 123-133.
85. S. van der Burg, E. Dolstra, S. McIntosh, J. Davies, D. M. German, and A. Hemel, “Tracing software build processes to uncover license compliance inconsistencies,” in Proc. of the 29th ACM/IEEE Intl. Conf. on Automated Software Engineering (ASE), 2014, pp. 731-742.
86. A. van der Hoek and A. L. Wolf, “Software release management for component-based software,” Softw. Pract. Exper., vol. 33, no. 1, pp. 77-98, Jan. 2003.
87. B. Vasilescu, Y. Yu, H. Wang, P. Devanbu, and V. Filkov, “Quality and productivity outcomes relating to continuous integration in github,” in Proc. of the Joint Meeting of the European Software Engineering Conf. and the Symp. on the Foundations of Software Engineering (ESEC/FSE), 2015, pp. 805-816.
88. J. A. Whittaker, J. Arbon, and J. Carollo, How Google Tests Software, 1st ed. Addison-Wesley Professional, 2012.
89. J. Wloka, B. Ryder, F. Tip, and X. Ren, “Safe-commit analysis to facilitate team software development,” in Proc. of the 31st Intl. Conf. on Software Engineering (ICSE), 2009, pp. 507-517.
90. XebiaLabs, “Periodic table of devops tools,” https://xebialabs.com/periodic-table-of-devops-tools/, 2015.
91. S. Yoo and M. Harman, “Regression testing minimization, selection and prioritization: A survey,” Softw. Test. Verif. Reliab., vol. 22, no. 2, pp. 67-120, Mar. 2012.