Abstract
To a user, unreleased software is nonexistent software, even in open source projects which make the source code readily accessible. Every project requires regular software releases to encourage adoption and attract developers. Different projects approach the task of releasing software in variousways [2], and many experience breakdowns in their release process at some point during their evolution [3]. This poster presents examples of these instances, and how projects are learning from and improving upon them.
Chapter PDF
Similar content being viewed by others
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
References
Choosing the FreeBSD Version That Is Right For You, http://www.freebsd.org/doc/en/articles/version-guide/
Erenkrantz, J.R.: Release Management Within Open Source Projects. In: Proceedings of the ICSE 3rd Workshop on Open Source Software Engineering (2003)
Michlmayr, M., Hunt, F., Probert, D.: Release Management in Free Software Projects: Practices and Problems. International Federation for Information Processing 234, 295 (2007)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 IFIP International Federation for Information Processing
About this paper
Cite this paper
Wright, H.K., Perry, D.E. (2009). Release Mismanagement in Open Source. In: Boldyreff, C., Crowston, K., Lundell, B., Wasserman, A.I. (eds) Open Source Ecosystems: Diverse Communities Interacting. OSS 2009. IFIP Advances in Information and Communication Technology, vol 299. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-02032-2_39
Download citation
DOI: https://doi.org/10.1007/978-3-642-02032-2_39
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-02031-5
Online ISBN: 978-3-642-02032-2
eBook Packages: Computer ScienceComputer Science (R0)