<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Paper on Software Engineering Group</title><link>https://seg.inf.unibe.ch/news/tags/paper/</link><description>Recent content in Paper on Software Engineering Group</description><generator>Hugo</generator><language>en-US</language><copyright>Software Engineering Group (SEG), [Institute of Computer Science](https://www.inf.unibe.ch/), [University of Bern](https://www.unibe.ch/). All rights reserved.</copyright><lastBuildDate>Mon, 27 Jul 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://seg.inf.unibe.ch/news/tags/paper/index.xml" rel="self" type="application/rss+xml"/><item><title>Conflict-Induced Variability: Our Vision Presented at ICSE 2026</title><link>https://seg.inf.unibe.ch/news/2026/07/27/conflict-induced-variability-our-vision-presented-at-icse-2026/</link><pubDate>Mon, 27 Jul 2026 12:00:00 +0200</pubDate><guid>https://seg.inf.unibe.ch/news/2026/07/27/conflict-induced-variability-our-vision-presented-at-icse-2026/</guid><description>&lt;p&gt;At ICSE 2026, we presented our NIER paper &lt;a href="https://dl.acm.org/doi/full/10.1145/3786582.3786840" title="Turning Merge Conflicts Into Conflict-Induced Variability" rel="external" target="_blank"&gt;&lt;span class="text-with-icon"&gt;&lt;svg width="800" height="800" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather feather-external-link"&gt;&lt;path d="M18 13v6a2 2 0 01-2 2H5a2 2 0 01-2-2V8a2 2 0 012-2h6"/&gt;&lt;polyline points="15 3 21 3 21 9"/&gt;&lt;line x1="10" y1="14" x2="21" y2="3"/&gt;&lt;/svg&gt;&lt;span&gt;Turning Merge Conflicts Into Conflict-Induced Variability&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;. The paper explores a new perspective on merge conflicts: instead of resolving them immediately, we propose to treat them as explicit variability that can be analyzed, managed, and resolved more systematically. By turning conflicts into first-class variability, developers can postpone resolution, compare alternatives, and make more informed integration decisions.&lt;/p&gt;</description></item></channel></rss>