Conference paper Open Access

How do developers fix issues and pay back technical debt in the Apache ecosystem?

Digkas, Georgios; Lungu, Mircea; Avgeriou, Paris; Chatzigeorgiou, Alexander; Ampatzoglou, Apostolos

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="URL"></identifier>
      <creatorName>Digkas, Georgios</creatorName>
      <affiliation>University of Groningen</affiliation>
      <creatorName>Lungu, Mircea</creatorName>
      <affiliation>University of Groningen</affiliation>
      <creatorName>Avgeriou, Paris</creatorName>
      <affiliation>University of Groningen</affiliation>
      <creatorName>Chatzigeorgiou, Alexander</creatorName>
      <affiliation>University of Macedonia</affiliation>
      <creatorName>Ampatzoglou, Apostolos</creatorName>
      <affiliation>University of Macedonia</affiliation>
    <title>How do developers fix issues and pay back technical debt in the Apache ecosystem?</title>
    <date dateType="Issued">2018-04-05</date>
  <resourceType resourceTypeGeneral="ConferencePaper"/>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsIdenticalTo">10.1109/SANER.2018.8330205</relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;During software evolution technical debt (TD) follows a constant ebb and flow, being incurred and paid back, sometimes in the same day and sometimes ten years later. There have been several studies in the literature investigating how technical debt in source code accumulates during time and the consequences of this accumulation for software maintenance. However, to the best of our knowledge there are no large scale studies that focus on the types of issues that are fixed and the amount of TD that is paid back during software evolution. In this paper we present the results of a case study, in which we analyzed the evolution of fifty-seven Java open-source software projects by the Apache Software Foundation at the temporal granularity level of weekly snapshots. In particular, we focus on the amount of technical debt that is paid back and the types of issues that are fixed. The findings reveal that a small subset of all issue types is responsible for the largest percentage of TD repayment and thus, targeting particular violations the development team can achieve higher benefits.&lt;/p&gt;</description>
      <funderName>European Commission</funderName>
      <funderIdentifier funderIdentifierType="Crossref Funder ID">10.13039/501100000780</funderIdentifier>
      <awardNumber awardURI="info:eu-repo/grantAgreement/EC/H2020/780572/">780572</awardNumber>
      <awardTitle>Software Development toolKit for Energy optimization and technical Debt elimination</awardTitle>
Views 78
Downloads 162
Data volume 107.6 MB
Unique views 66
Unique downloads 149


Cite as