Replaying past changes in multi-developer projects

  • Authors:
  • Lile Hattori;Mircea Lungu;Michele Lanza

  • Affiliations:
  • University of Lugano - Switzerland;University of Lugano - Switzerland;University of Lugano - Switzerland

  • Venue:
  • Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE)
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

What was I working on before the weekend? and What were the members of my team working on during the last week? are common questions that are frequently asked by a developer. They can be answered if one keeps track of who changes what in the source code. In this work, we present Replay, a tool that allows one to replay past changes as they happened at a fine-grained level, where a developer can watch what she has done or understand what her colleagues have done in past development sessions. With this tool, developers are able to not only understand what sequence of changes brought the system to a certain state (e.g., the introduction of a defect), but also deduce reasons for why her colleagues performed those changes. One of the applications of such a tool is also discovering the changes that broke the code of a developer.