Jump to: navigation, search

Difference between revisions of "Orion/Continuous Delivery"

(Testing)
Line 12: Line 12:
  
 
== Testing ==
 
== Testing ==
 +
=== Automated testing ===
 +
 +
=== Controlled access for new features ===
  
 
== Communication ==
 
== Communication ==

Revision as of 21:35, 15 July 2014

This page collects ideas, processes, and technology requirements for supporting continuous delivery of Orion

Overview

For the past couple of years, the Orion project has followed an abbreviated version of the classic Eclipse milestone development process. Each release consisted of two 6 week milestones, followed by a 5 week end-game, for a roughly 4 month total release cycle. This release cadence works well enough for classic software that is released and delivered to customers, but is not acceptable for Orion consumers building hosted software services. Four months is far too long to wait to update a web application. Other related web technology such as browsers and web frameworks are releasing much faster, and security bugs often require very fast (even zero day) turnaround.

This page captures the Orion community's efforts to move from three releases a year, to an interim goal of releasing stable builds once a week.

Planning

Builds

Testing

Automated testing

Controlled access for new features

Communication

New and noteworthy