As of May 9, 2015, Millersville University will adopt Continuous Delivery for its D2L system.
The information below comes from the document Continuous Delivery Overview by D2L, Inc.
What is Continuous Delivery?
Continuous Delivery is a design practice used in software development to automate and improve the process of software delivery. The Continuous Delivery model will allow D2L to deliver updated technology to clients, enabling rapid, incremental delivery of high quality, valuable new functionality to users. This frictionless model also makes it possible to increase collaboration with clients and to adapt software in line with user feedback and needs, resulting in incremental and easily integrated changes.
The Continuous Delivery model replaces the current system of "Big Bang releases" (large updates released once or twice a year) with regular monthly updates allowing for incremental and easily integrated changes.
How will this work?
Once a client adopts an initial Continuous Delivery release, the newest version will be delivered on a monthly basis. Clients will be able to access anything that would have previously been included in services packs, in addition to new tools, new features, and other product changes – but delivered in a smaller, incremental, and non-disruptive way.
Updates will be deployed to clients throughout each update period, following a recurring monthly schedule, and applied to both test and production instances. Clients will be assigned a "wave" and their updates will occur on the same day every month. This will provide clients with predictability for their implementations.
To effectively manage this increased frequency of change, we have enhanced our release documentation and other resources to support the adoption of these changes.
Why is D2L making the change? What are the benefits?
The primary benefit of the Continuous Delivery process is the shift from larger, disruptive, bi-annual upgrades to smaller and more easily integrated changes.
To further ensure that this process minimizes client and end user disruption, D2L will provide release documentation and other resources to support the adoption of changes.
Continuous Delivery makes it possible to adapt software more closely in line with user feedback.
Frequent feedback loops mean that it is possible to incorporate that feedback directly into the build and affect the relevance, quality, and successful adoption of the product.
Developers will grow closer to our clients and users, enhancing their understanding of what users really need.
Reliability and Stability
Continuous Delivery enables increased reliability and stability due to the frequency of releases. Making changes in small increments substantially reduces the potential risk of problems occurring.
Minimizing larger changes also makes it substantially easier to find and fix problems if they do occur - ensuring they have minimal impact on the user.
One single code-line of work ensures issues are resolved more rapidly and completely, eliminating the potential difficulty incurred by lagging versions.
The Continuous Delivery model will speed up the whole upgrade process. Test, support, development, and operations will work with each other as one team, in turn increasing the speed of delivery.
Automating the release process leads to greater speed and efficiency, saving developers time that can in turn be spent creating features that deliver better business value to clients.
Better quality products result from frequent user feedback, earlier releases, increased customer focus, and one single code-line for development. These factors combine to improve speed to market, innovation, and reliability.
Better User Experience
Ensuring clients have the latest software makes them better able to deliver the best possible experience to their users.