Click here to close now.


Linux Containers Authors: Pat Romanski, David Dodd, Liz McMillan, Elizabeth White, Anders Wallgren

Related Topics: Linux Containers

Linux Containers: Article

The OSS Development Life Cycle

Part 4 of 4

This is an excerpt from Chapter 6 of Understanding Open Source Software Development by Joseph Feller and Brian Fitzgerald, published by Addison-Wesley. ISBN 0201734966. No part of this excerpt may be reproduced, in any form or by any means without the prior written permission of the publisher. (c) 2002 Addison-Wesley

The traditional software development life cycle (SDLC) is premised on a set of stages, which, in their most generic form, include:

  • Planning
  • Analysis
  • Design
  • Implementation
However, the OSS development life cycle is quite different. First, the planning, analysis, and design phases are largely conducted by the initial project founder, and are not part of the general OSS development life cycle. Getting design issues right is perhaps even more critical in OSS than in conventional development. Certain criteria in relation to modularity of the code are critical. For example, modules must be loosely coupled, thereby allowing distributed development in the first place. Less important, but still highly desirable for achieving an efficient development model, is that modules be highly cohesive and address a single well-defined purpose. However, design decisions are generally made in advance, before the larger pool of developers start to contribute, and are generally based on well-established design patterns. This allows developers to collaborate without having to undergo the detailed requirements analysis or design phases of the traditional life cycle. In the absence of conventional project management, the importance of "having a tail-light to follow" (Bezroukov, 1999b) is a very useful coordinating principle, as it allows a multitude of developers to contribute. This also helps to explain why many OSS products are horizontal infrastructure-type products, as these are ones in which the requirements are pretty well understood. In vertical domains, developer knowledge of the application domain has been found to be critical, but it is unlikely that the pool of potential developers would be as high in such domains.

Thus, the OSS development life cycle is located primarily within the implementation phase of the traditional SDLC. Several researchers have investigated the life cycle underpinning OSS. Bollinger et al. (1999) suggest that it follows a very intensive spiral model (Boehm, 1988), albeit without any real risk assessment. Mockus et al. (2000) have derived a life cycle for OSS from their study of the Apache Project, and Jorgensen (2001) has investigated the life cycle in the FreeBSD Project. Both have come up with models that are largely compatible, but Jorgensen's is more detailed. He identifies the following main phases in the OSS development life cycle:


  • Review
  • Pre-commit test
  • Development release
  • Parallel debugging
  • Production release

    This is the sine qua non activity. However, many potential OSS contributors may fear taking the initial step of submitting their code for review by the supremely talented OSS "code-gods" (Asklund and Bendix, 2001; Bergquist and Ljungberg, 2001), a fear that is quite warranted when you consider the views of a FreeBSD developer reported by Jorgensen (2001):

    The way you get commit privileges is by first making enough code contributions&This implies the code you've been submitting is of sufficiently impressive quality that no one objects and says, "Yuck, no, don't give him commit privileges. He writes ugly code."

    Thus, the knowledge that talented and respected peers will be reviewing the code is a real incentive to improve the quality of the code being submitted in the first place.

    As already mentioned, truly independent peer review is one of the central strengths of the OSS process. However, Jorgensen found that eliciting feedback was not always easy. "Heavyweights" with a proven reputation will get a lot of feedback, but it can be quite difficult to get attention as a newbie - another classic "Catch-22" situation. Also, somewhat paradoxically, the simpler the code, the more feedback you gets. However, complex code would invariably benefit more from feedback. Also, it's more difficult to get feedback on design issues.

    Precommit Test
    Given the vulnerability of the OSS development model, it's critical that committers test each contribution carefully to avoid breaking the build, another common norm in the OSS community. Since there is no convenient help-line or telephone support for those installing the eventual product, it can be an adventure completing an actual OSS product installation. Sanders (1998) quotes the "tech-savvy" Ellen Ullman's description of her installation of Linux as "an exhilarating succession of problem-solving challenges." Given this problematic installation context, it is imperative that installation proceeds as smoothly as possible without unnecessary noise, and thus rogue modules that could jeopardize this must be prevented.

    Interestingly, testing is very much a personal process. There is no requirement that test scenarios be rigorously planned and written down in advance. However, the negative implications of allowing a faulty contribution through are such that the testing process is taken very seriously indeed. As mentioned earlier, the delegation of testing to the user community - or partial delegation, as is the case with Mozilla and GNOME - is one of the strengths of OSS (Schmidt and Porter, 2001).

    Development Release
    If the committer deems the module ready, it can be incorporated in the development release. This is the key payoff for many developers as they get the reward of seeing their code implemented quickly in the product. Jorgensen (2001) cites a developer who captures it quite graphically:

    There is a tremendous satisfaction to the "see bug, fix bug, see bug fix get incorporated so that the fix helps others" cycle.

    Parallel Debugging
    The advantages of global parallel debugging were discussed above. Again, as in testing, there is typically no formal plan for debugging. Rather the numbers of potential debuggers is where the power of the debugging arises - Linus's Law. If bugs are found, they can be fixed and resubmitted as per the life cycle described above, or problem reports may be created and submitted. This can also be a way of initiating your contributions to OSS. For example, the database of outstanding problem reports could be examined, and if there are some outstanding that catch your interest or are within your capability, then these can be worked on. Thus, can you begin a career in OSS.

    Production Release
    Contributions eventually become part of the production release. They are merged into the stable production branch. This is accomplished in different ways in different projects. FreeBSD maintains stable production and current development branches, and contributions that are eventually found suitable are merged into the latest stable production branch, and, in the case of a bug fix, to any previous production branches to which it might be relevant. Linux maintains its stable production and development versions in different directories, and uses release numbers to identify production (even numbers) and development (odd numbers) versions.

    We have argued that the generic OSS development process is characterized by the practice of parallel, rather than linear, collaboration among developers, which leads to increases in both speed and quality; by the participation of large, globally distributed communities of developers who participate in a truly independent peer review process; by prompt feedback (e.g., bug reports) and prompt recognition (e.g., integration of bug fixes); by the participation of talented and motivated developers and extremely active users; and by rapid, incremental release schedules. We also examined the well-stocked toolkit of OSS, including configuration management tools like CVS, as well as editors, build tools, documentation extractors, and the like. Finally, we argued that the OSS process is governed by an elaborate system of taboos and social mores that take the place of formal project management, and that the OSS process follows a distinctly different development life cycle to traditional proprietary software.

  • More Stories By Joseph Feller

    Joseph Feller is a lecturer with the Business Information Systems Group,
    University College Cork, Ireland. His research on Open Source Software is
    published in several prominent conference proceedings and he is the author
    of Customer Friendly: Design Guidelines for eCommerce. He also edits the
    monthly professional journal, Inside XML Solutions.

    More Stories By Brian Fitzgerald

    Brian Fitzgerald is the Frederick A Krehbiel II Professor of Innovation in Global Business and Technology at the University of Limerick, Ireland. He is Associate Editor for two leading international journals in the IS field, The Information Systems Journal, and Data Base. His publications include five books and more than 50 papers, published in leading international conferences and journals. Having worked in the industry prior to taking up an academic position, he has more than 20 years of experience in the IS field.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    @ThingsExpo Stories
    Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi’s VP Business Development and Engineering, explored the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context with p...
    I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
    Cloud computing delivers on-demand resources that provide businesses with flexibility and cost-savings. The challenge in moving workloads to the cloud has been the cost and complexity of ensuring the initial and ongoing security and regulatory (PCI, HIPAA, FFIEC) compliance across private and public clouds. Manual security compliance is slow, prone to human error, and represents over 50% of the cost of managing cloud applications. Determining how to automate cloud security compliance is critical to maintaining positive ROI. Raxak Protect is an automated security compliance SaaS platform and ma...
    The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
    Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
    DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, demonstrated examples of com...
    As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningful and actionable insights. In his session at @ThingsExpo, Paul Turner, Chief Marketing Officer at...
    In his keynote at @ThingsExpo, Chris Matthieu, Director of IoT Engineering at Citrix and co-founder and CTO of Octoblu, focused on building an IoT platform and company. He provided a behind-the-scenes look at Octoblu’s platform, business, and pivots along the way (including the Citrix acquisition of Octoblu).
    In his General Session at 17th Cloud Expo, Bruce Swann, Senior Product Marketing Manager for Adobe Campaign, explored the key ingredients of cross-channel marketing in a digital world. Learn how the Adobe Marketing Cloud can help marketers embrace opportunities for personalized, relevant and real-time customer engagement across offline (direct mail, point of sale, call center) and digital (email, website, SMS, mobile apps, social networks, connected objects).
    The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, exploreed the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
    Two weeks ago (November 3-5), I attended the Cloud Expo Silicon Valley as a speaker, where I presented on the security and privacy due diligence requirements for cloud solutions. Cloud security is a topical issue for every CIO, CISO, and technology buyer. Decision-makers are always looking for insights on how to mitigate the security risks of implementing and using cloud solutions. Based on the presentation topics covered at the conference, as well as the general discussions heard between sessions, I wanted to share some of my observations on emerging trends. As cyber security serves as a fou...
    We all know that data growth is exploding and storage budgets are shrinking. Instead of showing you charts on about how much data there is, in his General Session at 17th Cloud Expo, Scott Cleland, Senior Director of Product Marketing at HGST, showed how to capture all of your data in one place. After you have your data under control, you can then analyze it in one place, saving time and resources.
    With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now all corporate assets – people, objects, and spaces – can share information about themselves and thei...
    The cloud. Like a comic book superhero, there seems to be no problem it can’t fix or cost it can’t slash. Yet making the transition is not always easy and production environments are still largely on premise. Taking some practical and sensible steps to reduce risk can also help provide a basis for a successful cloud transition. A plethora of surveys from the likes of IDG and Gartner show that more than 70 percent of enterprises have deployed at least one or more cloud application or workload. Yet a closer inspection at the data reveals less than half of these cloud projects involve production...
    Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion is moderated by me, Dana Gardner, Principal Analyst at Interarbor Solutions.
    Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.
    Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
    Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" in this scenario: microservice A (releases daily) depends on a couple of additions to backend B (re...
    The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound effect on the world, and what should we expect to see over the next couple of years.
    Container technology is shaping the future of DevOps and it’s also changing the way organizations think about application development. With the rise of mobile applications in the enterprise, businesses are abandoning year-long development cycles and embracing technologies that enable rapid development and continuous deployment of apps. In his session at DevOps Summit, Kurt Collins, Developer Evangelist at, examined how Docker has evolved into a highly effective tool for application delivery by allowing increasingly popular Mobile Backend-as-a-Service (mBaaS) platforms to quickly crea...