Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 395

The DOI matches its Crossref record.

When do changes induce fixes?

Śliwerski, Jacek, Zimmermann, Thomas, Zeller, Andreas·2005·Proceedings of the 2005 international workshop on Mining software repositories - MSR '05

Abstract

As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes---changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/1083142.1083147

Cites

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cited by

See all 395

Metadata

Authors
Śliwerski, J., Zimmermann, T., & Zeller, A.
Venue
Proceedings of the 2005 international workshop on Mining software repositories - MSR '05
Publisher
ACM Press
Published
2005
Pages
1-5
OpenAlex
W4235354960
Cited by
395
References
0
FWCI
13.57
Type
conference paper
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: When do changes induce fixes? https://app.cochat.ai/papers/10.1145/1083142.1083147
The paper
Śliwerski, J., Zimmermann, T., & Zeller, A. (2005). When do changes induce fixes? Proceedings of the 2005 international workshop on Mining software repositories - MSR '05. https://doi.org/10.1145/1083142.1083147

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.