Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

DTP 1.10 Schedule and Rampdown Policy

Back to DTP Main Page


This document defines a schedule and set of ramp-down policies for DTP 1.10 (Juno). The goal is to ensure that DTP stability and completeness converges on the 1.10 release dates, while allowing mechanisms for changes as necessary.


DTP is on the Juno release train as a +1 project. These dates are based on the Juno Simultaneous Release Plan

  • 1.10M1 - August 15, 2011 (publicly available 8/19/11)
  • 1.10M2 - September 26, 2011 (publicly available 10/30/11)
  • 1.10M3 - November 7, 2011 (publicly available 11/11/11)
  • 1.10M4 - December 12, 2011 (publicly available 12/16/11)
  • 1.10M5 - January 30, 2012 (publicly available 2/3/12)
  • 1.10M6 - March 19, 2012 (publicly available 3/23/12)
  • 1.10M7 - May 7, 2012 (publicly available 5/11/12)
  • 1.10RC1 - May 21, 2012 (publicly available 5/25/12)
  • 1.10RC2 - May 28, 2012 (publicly available 6/1/12)
  • 1.10RC3 - June 4, 2012 (publicly available 6/8/12)
  • 1.10RC4 - June 11, 2012 (publicly available 6/15/12)
  • 1.10 Release - June 27, 2012

Builds Reminder

  • Nightly builds take place from Monday to Thursday. Integration builds takes place on Friday.
  • During a test phase, there are no builds. We take the build before the test phase and test it. If we run across extreme issues, we will re-spin and retest.
  • During the test/fix phase for the RCs, we will do regular daily builds. Once we are in the test/fix phase, where PMC approvals are needed, we will not build nightly, but will build as needed (RC1 and beyond).
  • On Push days, we will take the Monday Shanghai build (which is our Sunday at 2pm PST) and if it's good, we will push it to the update site that Monday evening (SH Tuesday a.m.). If things are not good, we will fix the issues and re-spin the build, taking the re-spun build and pushing it to the update site.
  • DTP builds will take place at 5am (Shanghai time).
  • In general, builds occur Mon - Fri at 2pm Shanghai time, which is equivalent to Sun - Thu 2pm PST.
  • DTP committers should refrain from updating map files for +/- 30 minutes around the start of the build, to avoid version inconsistencies in the map file set.
  • See the Build Transition page for additional details about regular DTP builds

Integration Builds

Starting with RC1, the latest available DTP integration build (done each Friday, as noted above) will be tested for promotion. If no substantial defects are found, then the build will be promoted.

Testing & Fix Pass

A period of intensive testing, including bug fixes based on the approval policies described below. Nightly builds will be produced during this period as necessary to make bug fixes available to the DTP community.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.