Access keys for a quick navigation0: Top of pagen: Main navigationDirect links to main chapters: h: home; 1; about OLAT; 2: download; 3: developmentSearch field: so: Top navigationm: Menuc: Content areab: One step back (if available)
THIRDROW
OLAT Logo

Incubation Process

This is a typical OLAT release cycle:

  1. Before code freeze: for each incubation candidate a Jira issue is created with version set to "Incubation". Reviewers and testers are defined.
  2. Before code freeze: link to Jira issue is published on the developers list and discussed by the community (via comments in Jira).
  3. CODE FREEZE about two months before semester start
    (for 6.2: mid-July 2009; for 6.3: mid-December 2009; for 6.4: Beginning of June 2010)
  4. After code freeze: CVS branch is opened for each feature. Small enhancements/bugs can be integrated into one branch.
  5. After code freeze: URL of branch instance is introduced to involved reviewers and testers.
  6. After code freeze: testing - bug fixing - testing cycles.
  7. GO LIVE of Release Candidate at University of Zurich; about one month before semester start
    (for 6.2: mid-August 2009; for 6.3: end of January 2009; for 6.4: mid-August 2010)
  8. Beta testing of Release Candidate at University of Zurich
  9. PUBLIC RELEASE max. one month after semester start
    (for 6.2: end of September 2009; for 6.3: mid-March 2009, for 6.4: Beginning of August 2010)
  10. After public release: merge each feature branch to head

The following picture illustrates the incubation process and release cycle:

OLAT incubation process and release cycle for OLAT 6.1OLAT incubation process and release cycle for OLAT 6.1
RSS