<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-10-05T21:32:31Z</responseDate>
  <request identifier="27994" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:27994</identifier>
        <datestamp>2026-10-05T06:44:03Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>How Developers Use Relation Chains in Gerrit-Based Review Ecosystems: An Empirical Study Across Three Open-Source Ecosystems</dc:title>
          <dc:creator>Belhouchette, Ahmed</dc:creator>
          <dc:creator>Chouchen, Moataz</dc:creator>
          <dc:creator>Chaieb, Marouene</dc:creator>
          <dc:creator>Hamdaqa, Mohammad</dc:creator>
          <dc:creator>Hamou-Lhadj, Abdelwahab</dc:creator>
          <dc:subject>Code review</dc:subject>
          <dc:subject>relation chains</dc:subject>
          <dc:subject>stacked changes</dc:subject>
          <dc:subject>dependent patches</dc:subject>
          <dc:subject>empirical software engineering</dc:subject>
          <dc:subject>Gerrit</dc:subject>
          <dc:description>Background. Developers increasingly coordinate dependent review workflows by submitting sequences of related changes rather than monolithic ones. In Gerrit, these dependencies form relation chains: structured review units that link changes together. As chains become more common, they shape review activities through synchronization overhead, CI amplification, and merge-ordering constraints. &#13;
&#13;
Aim. We investigate how developers adopt relation chains and how these dependency structures influence review dynamics and outcomes. &#13;
&#13;
Method. We analyze 29,580 relation chains from 15 repositories across three Gerrit ecosystems (OpenStack, Wikimedia, ONAP), comprising 401,256 changes, using Mann-Kendall trend tests, Mann-Whitney with Cliff’s δ for chain-vs-solo comparison, and Spearman correlations for base-descendant dependency. &#13;
&#13;
Results. Chain prevalence ranges from 5% to 49% across projects, increasing in 14 of 15. Chain changes take a median of 2.6× longer to merge than size-matched solo changes, with the gap widening for very large changes. Review effort propagates through dependency-linked review workflows: base-change review activity co-varies with descendant review activity (ρ = 0.43-0.61 in 14-15/15 projects), and 33.5% of chain members undergo structural evolution during review. &#13;
&#13;
Conclusions. Relation chains operate as durable, ecosystem-shaped coordination units with internal structure that change-centric analyses cannot capture. Future review analytics, reviewer-assignment systems, and AI-assisted review tools should reason over chains rather than isolated changes.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Ahmed Belhouchette and Moataz Chouchen and Marouene Chaieb and Mohammad Hamdaqa and Abdelwahab Hamou-Lhadj</dc:contributor>
          <dc:date>2026</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 394, 20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ESEM.2026.26</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-279942</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ESEM.2026.26</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
