Don’t Program on Fridays! How to Locate Fix-Inducing Changes

dc.contributor.author	Śliwerski, Jacek
dc.contributor.author	Zimmermann, Thomas
dc.contributor.author	Zeller, Andreas
dc.contributor.editor	Kelter, Udo
dc.date.accessioned	2024-10-25T08:11:31Z
dc.date.available	2024-10-25T08:11:31Z
dc.date.issued	2005
dc.description.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 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 ECLIPSE history, it turns out that fix-inducing changes are most frequent on Fridays.	en
dc.identifier.doi	10.18420/swt25-2_25
dc.identifier.doi	10.18420/swt25-2_25
dc.identifier.uri	https://dl.gi.de/handle/20.500.12116/45310
dc.language.iso	en
dc.pubPlace	Bonn
dc.publisher	Gesellschaft für Informatik e.V.
dc.relation.ispartof	Softwaretechnik-Trends Band 25, Heft 2
dc.relation.ispartofseries	Softwaretechnik-Trends
dc.subject	change
dc.subject	version management
dc.subject	defect
dc.subject	fix
dc.title	Don’t Program on Fridays! How to Locate Fix-Inducing Changes	en
dc.type	Text/Conference Paper
mci.conference.date	2.-4. Mai 2005
mci.conference.location	Bad Honnef
mci.conference.sessiontitle	7. Workshop Software Engineering (WSR 2005) der GI-Fachgruppe Software-Reengineering (SRE)
mci.reference.pages	55-56

Dateien

1 - 1 von 1