Automated Categorisation of Breaking Merge Commits (Work in Progress)

Ward Muylaert; Coen De Roover

Abstract

Integrating code from different sources can be an error-prone and effort-intensive process.
While an integration may appear sound, unexpected errors may still surface at run time.
What exactly constitutes these errors is not always clear, nor is it known which are most common.
We want to create a hierarchic categorisation of errors that break merge commits.
We will do this in two phases.
First, a manual categorisation to enable the definition of categories based on real world examples.
Second, a declarative specification of every category to automate categorisation and enable performing an empirical study.

Original language	English
Publication status	Unpublished - 2017
Event	Seminar Series on Advanced Techniques & Tools for Software Evolution - Madrid, Spain, Madrid, Spain Duration: 7 Jun 2017 → 9 Jun 2017 Conference number: 10 http://sattose.org/2017

Seminar

Seminar	Seminar Series on Advanced Techniques & Tools for Software Evolution
Abbreviated title	SATToSE
Country	Spain
City	Madrid
Period	7/06/17 → 9/06/17
Internet address	http://sattose.org/2017

Access to Document

submittedSubmitted manuscript, 62.8 KB

1 Talk or presentation at a workshop/seminar

Seminar Series on Advanced Techniques & Tools for Software Evolution
Ward Muylaert (Speaker)
7 Jun 2017 → 9 Jun 2017
Activity: Talk or presentation › Talk or presentation at a workshop/seminar

Cite this

@conference{ee98ffc7354f41d2939757a71c0a6b71,

title = "Automated Categorisation of Breaking Merge Commits (Work in Progress)",

abstract = "Integrating code from different sources can be an error-prone and effort-intensive process. While an integration may appear sound, unexpected errors may still surface at run time. What exactly constitutes these errors is not always clear, nor is it known which are most common. We want to create a hierarchic categorisation of errors that break merge commits. We will do this in two phases. First, a manual categorisation to enable the definition of categories based on real world examples. Second, a declarative specification of every category to automate categorisation and enable performing an empirical study.",

author = "Ward Muylaert and {De Roover}, Coen",

year = "2017",

language = "English",

note = "Seminar Series on Advanced Techniques & Tools for Software Evolution, SATToSE ; Conference date: 07-06-2017 Through 09-06-2017",

url = "http://sattose.org/2017",

}

TY - CONF

T1 - Automated Categorisation of Breaking Merge Commits (Work in Progress)

AU - Muylaert, Ward

AU - De Roover, Coen

PY - 2017

Y1 - 2017

N2 - Integrating code from different sources can be an error-prone and effort-intensive process. While an integration may appear sound, unexpected errors may still surface at run time. What exactly constitutes these errors is not always clear, nor is it known which are most common. We want to create a hierarchic categorisation of errors that break merge commits. We will do this in two phases. First, a manual categorisation to enable the definition of categories based on real world examples. Second, a declarative specification of every category to automate categorisation and enable performing an empirical study.

AB - Integrating code from different sources can be an error-prone and effort-intensive process. While an integration may appear sound, unexpected errors may still surface at run time. What exactly constitutes these errors is not always clear, nor is it known which are most common. We want to create a hierarchic categorisation of errors that break merge commits. We will do this in two phases. First, a manual categorisation to enable the definition of categories based on real world examples. Second, a declarative specification of every category to automate categorisation and enable performing an empirical study.

M3 - Unpublished abstract

ER -

Automated Categorisation of Breaking Merge Commits (Work in Progress)

Abstract

Seminar

Access to Document

Fingerprint

Activities

Seminar Series on Advanced Techniques & Tools for Software Evolution

Cite this