Untangling Fine-Grained Code Changes
Type de document :
Communication dans un congrès avec actes
Titre :
Untangling Fine-Grained Code Changes
Auteur(s) :
Dias, Martín [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Bacchelli, Alberto [Auteur]
Gousios, Georgios [Auteur]
Digital Security Group [Nijmegen]
Cassou, Damien [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Bacchelli, Alberto [Auteur]
Gousios, Georgios [Auteur]
Digital Security Group [Nijmegen]
Cassou, Damien [Auteur]

Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]

Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Titre de la manifestation scientifique :
SANER: International Conference on Software Analysis, Evolution, and Reengineering
Ville :
Montréal
Pays :
Canada
Date de début de la manifestation scientifique :
2015-03-02
Titre de l’ouvrage :
SANER
Date de publication :
2015-03-02
Mot(s)-clé(s) en anglais :
version control system
atomic commits
untangling commits
pharo
atomic commits
untangling commits
pharo
Discipline(s) HAL :
Informatique [cs]/Langage de programmation [cs.PL]
Informatique [cs]/Génie logiciel [cs.SE]
Informatique [cs]/Génie logiciel [cs.SE]
Résumé en anglais : [en]
After working for some time, developers commit their code changes to a version control system. When doing so, they often bundle unrelated changes (e.g., bug fix and refactoring) in a single commit, thus creating a so-called ...
Lire la suite >After working for some time, developers commit their code changes to a version control system. When doing so, they often bundle unrelated changes (e.g., bug fix and refactoring) in a single commit, thus creating a so-called tangled commit. Sharing tangled commits is problematic because it makes review, reversion, and integration of these commits harder and historical analyses of the project less reliable. Researchers have worked at untangling existing commits, i.e., finding which part of a commit relates to which task. In this paper, we contribute to this line of work in two ways: (1) A publicly available dataset of untangled code changes, created with the help of two developers who accurately split their code changes into self contained tasks over a period of four months; (2) a novel approach, EpiceaUntangler, to help developers share untangled commits (aka. atomic commits) by using fine-grained code change information. EpiceaUntangler is based and tested on the publicly available dataset, and further evaluated by deploying it to 7 developers, who used it for 2 weeks. We recorded a median success rate of 91% and average one of 75%, in automatically creating clusters of untangled fine-grained code changes.Lire moins >
Lire la suite >After working for some time, developers commit their code changes to a version control system. When doing so, they often bundle unrelated changes (e.g., bug fix and refactoring) in a single commit, thus creating a so-called tangled commit. Sharing tangled commits is problematic because it makes review, reversion, and integration of these commits harder and historical analyses of the project less reliable. Researchers have worked at untangling existing commits, i.e., finding which part of a commit relates to which task. In this paper, we contribute to this line of work in two ways: (1) A publicly available dataset of untangled code changes, created with the help of two developers who accurately split their code changes into self contained tasks over a period of four months; (2) a novel approach, EpiceaUntangler, to help developers share untangled commits (aka. atomic commits) by using fine-grained code change information. EpiceaUntangler is based and tested on the publicly available dataset, and further evaluated by deploying it to 7 developers, who used it for 2 weeks. We recorded a median success rate of 91% and average one of 75%, in automatically creating clusters of untangled fine-grained code changes.Lire moins >
Langue :
Anglais
Comité de lecture :
Oui
Audience :
Internationale
Vulgarisation :
Non
Collections :
Source :
Fichiers
- https://hal.inria.fr/hal-01116225/document
- Accès libre
- Accéder au document
- http://arxiv.org/pdf/1502.06757
- Accès libre
- Accéder au document
- https://hal.inria.fr/hal-01116225/document
- Accès libre
- Accéder au document
- https://hal.inria.fr/hal-01116225/document
- Accès libre
- Accéder au document
- document
- Accès libre
- Accéder au document
- main.pdf
- Accès libre
- Accéder au document
- 1502.06757
- Accès libre
- Accéder au document
- document
- Accès libre
- Accéder au document
- main.pdf
- Accès libre
- Accéder au document