Modeling and Analyzing Release Trajectory based on the Process of Issue Tracking

Software release development process, that we refer to as "release trajectory", involves development activities that are usually sorted in different categories, such as incorporating new features, improving software, or fixing bugs, and associated to "issues". Release trajectory management is a difficult and crucial task. Managers must be aware of every aspect of the development process for managing the software-related issues. Issue Tracking Systems (ITS) play a central role in supporting the management of release trajectory. These systems, which support reporting and tracking issues of different kinds (such as "bug", "feature", "improvement", etc.), record rich data about the software development process. Yet, recorded historical data in ITS are still not well-modeled for supporting practical needs of release trajectory management. In this paper, we describe a sequence analysis approach for modeling and analyzing releases' trajectories, using the tracking process of reported issues. Release trajectory analysis is based on the categories of tracked issues and their temporal changing, and aims to address important questions regarding the co-habitation of unresolved issues, the transitions between different statuses in release trajectory, the recurrent patterns of release trajectories, and the properties of a release trajectory.

[1]  Shinji Kusumoto,et al.  How Much Do Code Repositories Include Peripheral Modifications? , 2013, 2013 20th Asia-Pacific Software Engineering Conference (APSEC).

[2]  Ali Shokoufandeh,et al.  Studying the Evolution of Software Systems Using Change Clusters , 2006, 14th IEEE International Conference on Program Comprehension (ICPC'06).

[3]  Andreas Zeller,et al.  The impact of tangled code changes , 2013, 2013 10th Working Conference on Mining Software Repositories (MSR).

[4]  Gabriele Bavota,et al.  Automatic generation of release notes , 2014, SIGSOFT FSE.

[5]  Michael W. Godfrey,et al.  Automatic classication of large changes into maintenance categories , 2009, 2009 IEEE 17th International Conference on Program Comprehension.

[6]  Michael W. Godfrey,et al.  Mining recurrent activities: Fourier analysis of change events , 2009, 2009 31st International Conference on Software Engineering - Companion Volume.

[7]  Michael W. Godfrey,et al.  Situational awareness: Personalizing issue tracking systems , 2013, 2013 35th International Conference on Software Engineering (ICSE).

[8]  Miguel Goulão,et al.  Software Evolution Prediction Using Seasonal Time Analysis: A Comparative Study , 2012, 2012 16th European Conference on Software Maintenance and Reengineering.

[9]  Michele Lanza,et al.  Software bugs and evolution: a visual approach to uncover their relationship , 2006, Conference on Software Maintenance and Reengineering (CSMR'06).

[10]  Jonathan I. Maletic,et al.  Using stereotypes to help characterize commits , 2011, 2011 27th IEEE International Conference on Software Maintenance (ICSM).

[11]  Eleni Stroulia,et al.  Understanding phases and styles of object-oriented systems' evolution , 2004, 20th IEEE International Conference on Software Maintenance, 2004. Proceedings..

[12]  Zhongpeng Lin.  Understanding and simulating software evolution , 2013, 2013 35th International Conference on Software Engineering (ICSE).

[13]  Michele Lanza,et al.  On the nature of commits , 2008, 2008 23rd IEEE/ACM International Conference on Automated Software Engineering - Workshops.

[14]  Foutse Khomh,et al.  Do faster releases improve software quality? An empirical case study of Mozilla Firefox , 2012, 2012 9th IEEE Working Conference on Mining Software Repositories (MSR).

[15]  Richard S. Hall,et al.  Software release management , 1997, ESEC '97/FSE-5.

[16]  Ivanka Menken,et al.  Release Management Best Practice Handbook: Building, Running and Managing Effective Software Release Management and Support - Ready to use supporting documents bringing ITIL Theory into Practice , 2008 .

[17]  Gilbert Ritschard,et al.  Analyzing and Visualizing State Sequences in R with TraMineR , 2011 .

[18]  Chris F. Kemerer,et al.  On the uniformity of software evolution patterns , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[19]  Chris F. Kemerer,et al.  An Empirical Approach to Studying Software Evolution , 1999, IEEE Trans. Software Eng..

[20]  Israel Herraiz Tabernero.  A statistical examination of the evolution and properties of libre software , 2012 .

[21]  Shinji Kusumoto,et al.  Hey! are you committing tangled changes? , 2014, ICPC 2014.

[22]  Michael W. Godfrey,et al.  Release Pattern Discovery via Partitioning: Methodology and Case Study , 2007, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007).

[23]  Huzefa H. Kagdi,et al.  On mapping releases to commits in open source systems , 2014, ICPC 2014.