Subversion 1.5: A case study in open source release mismanagement

Authors:
Hyrum K. Wright;Dewayne E. Perry
Affiliations:
Empirical Software Engineering Laboratory, Department of Electrical and Computer Engineering, The University of Texas at Austin, 78712 USA;Empirical Software Engineering Laboratory, Department of Electrical and Computer Engineering, The University of Texas at Austin, 78712 USA
Venue:
FLOSS '09 Proceedings of the 2009 ICSE Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development
Year:
2009

Citing 1
Cited 4

Why is Software Late? An Empirical Study of Reasons for Delay in Software Development

IEEE Transactions on Software Engineering

Release engineering processes, models, and metrics

Proceedings of the doctoral symposium for ESEC/FSE on Doctoral symposium
Experiences mining open source release histories

Proceedings of the 2011 International Conference on Software and Systems Process
Information needs for integration decisions in the release process of large-scale parallel development

Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Release engineering practices and pitfalls

Proceedings of the 34th International Conference on Software Engineering

Quantified Score

Hi-index	0.01

Visualization

Abstract

In June 2008, the Subversion development team released Subversion 1.5.0. This release contained a number of new features, but arrived only after a long and difficult development, test and release cycle. This protracted process confused and frustrated both users and developers. In this paper, we discuss the events which led to this breakdown, how the release process is being improved, and what lessons other open source projects can learn from the Subversion community's mistakes.