skip to main content
10.1145/2597008.2597792acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

On mapping releases to commits in open source systems

Published: 02 June 2014 Publication History

Abstract

The paper presents an empirical study on the release naming and structure in three open source projects: Google Chrome, GNU gcc, and Subversion. Their commonality and variability are discussed. An approach is developed that establishes the mapping from a particular release (major or minor) to the specific earliest and latest revisions, i.e., a commit window of a release, in the source control repository. For example, the major release 25.0 in Chrome is mapped to the earliest revision 157687 and latest revision 165096 in the trunk. This mapping between releases and commits would facilitate a systematic choice of history in units of the project evolution scale (i.e., commits that constitute a software release). A projected application is in forming a training set for a source-code change prediction model, e.g., using the association rule mining or machine learning techniques, commits from the source code history are needed.

References

[1]
T. Zimmermann, A. Zeller, P. Weissgerber, and S. Diehl. Mining version histories to guide software changes. Software Engineering, IEEE Transactions on, 31(6):429–445, 2005.
[2]
Huzefa Kagdi, Michael L. Collard, and Jonathan I. Maletic. A survey and taxonomy of approaches for mining software repositories in the context of software evolution. Journal of Software Maintenance and Evolution: Research and Practice, 19(2):77–131, 2007.
[3]
L.P. Hattori and M. Lanza. On the nature of commits. In Automated Software Engineering - Workshops, 2008. ASE Workshops 2008. 23rd IEEE/ACM International Conference on, pages 63–71, 2008.
[4]
A. Alali, H. Kagdi, and J.I. Maletic. What’s a typical commit? a characterization of open source software repositories. In Program Comprehension, 2008. ICPC 2008. The 16th IEEE International Conference on, pages 182–191, 2008.
[5]
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Software Maintenance, 1998. Proceedings., International Conference on, pages 190–198, 1998.
[6]
H. Gall, M. Jazayeri, R.R. Klosch, and G. Trausmuth. Software evolution observations based on product release history. In Software Maintenance, 1997. Proceedings., International Conference on, pages 160–166, 1997.
[7]
O. Saliu and G. Ruhe. Supporting software release planning decisions for evolving systems. In Software Engineering Workshop, 2005. 29th Annual IEEE/NASA, pages 14–26, 2005.

Cited By

View all
  • (2023)On the assignment of commits to releasesEmpirical Software Engineering10.1007/s10664-022-10263-x28:2Online publication date: 16-Jan-2023
  • (2021)Assessing time-based and range-based strategies for commit assignment to releases2021 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)10.1109/SANER50967.2021.00022(142-153)Online publication date: Mar-2021
  • (2018)Effectiveness of exploring historical commits for developer recommendationFrontiers of Computer Science: Selected Publications from Chinese Universities10.1007/s11704-016-6023-312:3(528-544)Online publication date: 1-Jun-2018
  • Show More Cited By

Index Terms

  1. On mapping releases to commits in open source systems

      Recommendations

      Comments

      Information & Contributors

      Information

      Published In

      cover image ACM Conferences
      ICPC 2014: Proceedings of the 22nd International Conference on Program Comprehension
      June 2014
      325 pages
      ISBN:9781450328791
      DOI:10.1145/2597008
      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

      Sponsors

      In-Cooperation

      • TCSE: IEEE Computer Society's Tech. Council on Software Engin.

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      Published: 02 June 2014

      Permissions

      Request permissions for this article.

      Check for updates

      Author Tags

      1. Commit History
      2. Empirical Studies
      3. Mining Software Repositories
      4. Software Releases

      Qualifiers

      • Article

      Conference

      ICSE '14
      Sponsor:

      Upcoming Conference

      ICSE 2025

      Contributors

      Other Metrics

      Bibliometrics & Citations

      Bibliometrics

      Article Metrics

      • Downloads (Last 12 months)8
      • Downloads (Last 6 weeks)0
      Reflects downloads up to 20 Jan 2025

      Other Metrics

      Citations

      Cited By

      View all
      • (2023)On the assignment of commits to releasesEmpirical Software Engineering10.1007/s10664-022-10263-x28:2Online publication date: 16-Jan-2023
      • (2021)Assessing time-based and range-based strategies for commit assignment to releases2021 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)10.1109/SANER50967.2021.00022(142-153)Online publication date: Mar-2021
      • (2018)Effectiveness of exploring historical commits for developer recommendationFrontiers of Computer Science: Selected Publications from Chinese Universities10.1007/s11704-016-6023-312:3(528-544)Online publication date: 1-Jun-2018
      • (2015)Detection of software evolution phases based on development activitiesProceedings of the 2015 IEEE 23rd International Conference on Program Comprehension10.5555/2820282.2820288(15-24)Online publication date: 16-May-2015
      • (2015)How Often does a Source Code Unit Change within a Release Window?Proceedings of the 8th India Software Engineering Conference10.1145/2723742.2723759(166-175)Online publication date: 18-Feb-2015
      • (2015)Detection of Software Evolution Phases Based on Development ActivitiesProceedings of the 2015 IEEE 23rd International Conference on Program Comprehension10.1109/ICPC.2015.11(15-24)Online publication date: 18-May-2015
      • (2014)Predicting Vulnerable ComponentsProceedings of the 2014 IEEE 25th International Symposium on Software Reliability Engineering10.1109/ISSRE.2014.32(23-33)Online publication date: 3-Nov-2014

      View Options

      Login options

      View options

      PDF

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader

      Media

      Figures

      Other

      Tables

      Share

      Share

      Share this Publication link

      Share on social media