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.
|