How Do Developers Use Migration Guides? A Case Study of Log4j
Takahiro Monno, Kazumasa Shimari, Tetsuya Kanda, Kazuma Yamasaki, Kenichi Matsumoto

TL;DR
This study investigates how developers utilize migration guides, focusing on Log4j, revealing that guides are frequently referenced throughout the migration process, often linked in pull requests, and used beyond major updates.
Contribution
The paper provides an empirical analysis of migration guide usage in real-world projects, highlighting their ongoing importance beyond initial version upgrades.
Findings
Most references to migration guides are links to the entire document.
Developers use migration guides during both major updates and maintenance.
Pull request descriptions frequently cite migration guides.
Abstract
Migration guides are a form of software documentation that helps developers address breaking changes introduced in library version updates. Prior studies have examined documents such as release notes, API reference manuals, and patch notes. However, research that focuses specifically on migration guides remains limited. Improving the usability and coverage of migration guides is essential for helping developers resolve breaking changes efficiently. Yet, we still lack a clear understanding of how migration guides are currently provided and how developers use them in practice. To fill this gap, we first investigate whether libraries known to introduce incompatibilities provide migration guides. We then conduct a detailed case study on Log4j, a library that has experienced large-scale breaking updates in the past. We empirically analyze how developers refer to and use the official…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
