@conference {966, title = {Replaying IDE interactions to evaluate and improve change prediction approaches}, booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)}, year = {2010}, pages = {161 - 170}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {Change prediction helps developers by recommending program entities that will have to be changed alongside the entities currently being changed. To evaluate their accuracy, current change prediction approaches use data from versioning systems such as CVS or SVN. These data sources provide a coarse-grained view of the development history that flattens the sequence of changes in a single commit. They are thus not a valid basis for evaluation in the case of development-style prediction, where the order of the predictions has to match the order of the changes a developer makes. We propose a benchmark for the evaluation of change prediction approaches based on fine-grained change data recorded from IDE usage. Moreover, the change prediction approaches themselves can use the more accurate data to fine-tune their prediction. We present an evaluation procedure and use it on several change prediction approaches, both novel and from the literature, and report on the results.}, keywords = {cbse, change based software evolution, change prediction, changes, commit, cvs, development history, eclipseeye, ide, mylyn, spyware, svn}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463278}, attachments = {https://flosshub.org/sites/flosshub.org/files/161Robbes2010changePrediction.pdf}, author = {Robbes, Romain and Pollet, Damien and Lanza, Michele} } @conference {971, title = {Branching and merging in the repository}, booktitle = {the 2008 international workshopProceedings of the 2008 international workshop on Mining software repositories - MSR {\textquoteright}08}, year = {2008}, month = {05/2008}, pages = {19-22}, publisher = {ACM Press}, organization = {ACM Press}, address = {New York, New York, USA}, abstract = {Two of the most complex operations version control software allows a user to perform are branching and merging. Branching provides the user the ability to create a copy of the source code to allow changes to be stored in version control but outside of the trunk. Merging provides the user the ability to copy changes from a branch to the trunk. Performing a merge can be a tedious operation and one that may be error prone. In this paper, we compare file revisions found on branches with those found on the trunk to determine when a change that is applied to a branch is moved to the trunk. This will allow us to study how developers use merges and to determine if merges are in fact more error prone than other commits.}, keywords = {argouml, changes, cvs2svn, diffj, revision, scm, source code, version control}, isbn = {9781605580241}, doi = {10.1145/1370750.1370754}, attachments = {https://flosshub.org/sites/flosshub.org/files/p19-williams.pdf}, author = {Spacco, Jamie and Williams, Chadd C.} } @conference {970, title = {Determinism and evolution}, booktitle = {Proceedings of the 2008 international workshop on Mining software repositories - MSR {\textquoteright}08}, year = {2008}, month = {05/2008}, pages = {1-9}, publisher = {ACM Press}, organization = {ACM Press}, address = {New York, New York, USA}, abstract = {It has been proposed that software evolution follows a Self-Organized Criticality (SOC) dynamics. This fact is supported by the presence of long range correlations in the time series of the number of changes made to the source code over time. Those long range correlations imply that the current state of the project was determined time ago. In other words, the evolution of the software project is governed by a sort of determinism. But this idea seems to contradict intuition. To explore this apparent contradiction, we have performed an empirical study on a sample of 3,821 libre (free, open source) software projects, finding that their evolution projects is short range correlated. This suggests that the dynamics of software evolution may not be SOC, and therefore that the past of a project does not determine its future except for relatively short periods of time, at least for libre software.}, keywords = {changes, evolution, source code, sourceforge}, isbn = {9781605580241}, doi = {10.1145/1370750.1370752}, attachments = {https://flosshub.org/sites/flosshub.org/files/p1-herraiz.pdf}, author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles and Herraiz, Israel} }