Sharif Digital Repository

As one of the most important software artifacts, release reports include most essential changes of software systems in each release. These reports are useful for documenting team activities, improving communication between team members and facilitating decision makings. They are often generated manually by a team member, which can be a tedious and time-consuming task. For each release, one should go through hundreds of issue reports, changed files, source code, and other related documents to determine what has changed and why. Then they need to identify the most important and relevant changes. Therefore, automated generation of release reports can be highly desirable. Despite the... 

An issue report documents the discussions around required changes in issue-tracking systems, while a commit contains the change itself in the version control systems. Recovering links between issues and commits can facilitate many software evolution tasks such as bug localization, defect prediction, software quality measurement, and software documentation. A previous study on over half a million issues from GitHub reports only about 42.2% of issues are manually linked by developers to their pertinent commits. Automating the linking of commit-issue pairs can contribute to the improvement of the said tasks by increasing the coverage of commit-issue links.By far, current state-of-the-art...