On mapping releases to commits in open source systems

Joe F. Shobe, Md Yasser Karim, Motahareh Bahrami Zanjani, Huzefa Kagdi
2014 Proceedings of the 22nd International Conference on Program Comprehension - ICPC 2014  
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
more » ... 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.
doi:10.1145/2597008.2597792 dblp:conf/iwpc/ShobeKZK14 fatcat:jemi57jfxvbtldpnifrsyyh72u