Jump to: navigation, search

Difference between revisions of "Orion/Plan"

(Past releases: fix bad release links)
 
(6 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
== Current and future releases ==
 
== Current and future releases ==
  
* [http://projects.eclipse.org/projects/eclipse.orion/releases/4.0.0 R4.0 Plan and Dates]
+
* All release plans beyond Orion 5.0 are found on the [https://projects.eclipse.org/projects/ecd.orion Orion project overview page]
 +
* [[Orion/Plan/Language_Tools|Language Tools]] - Roadmap for language tools in the Orion editor
  
== Past releases ==
+
== Release Wind-down ==
 +
As the development cycle gets closer to the release date, there is a general process we follow to ensure a successful and stable release.
  
 +
When development reaches the final thirty days before release, two important steps begin the wind-down:
 +
# The [https://projects.eclipse.org/projects/ecd.orion/generate-iplog IP log is submitted]. Before the logs are submitted, all outstanding dependencies must be checked and a decision made if they will appear in the upcoming release.
 +
# A release review must be scheduled. This is done from the [https://projects.eclipse.org/projects/ecd.orion project page] under a specific release.
 +
 +
 +
During the last thirty days, development follows a different schedule.
 +
To make sure we do not introduce any regressions right before the release, we do the following:
 +
# Keep working as usual for the first week of the wind-down. Typically no new features will be added at this time unless approved by the project lead
 +
# Once the release review is complete (typically by the second week of the wind-down), development changes to the "last chance" stage to put in changes (with no new features), with each change requiring a +1 from one other committer. This continues for the next two weeks.
 +
# The last week is reserved strictly for testing and making critical fixes, with any fix requiring a +1 from two committers (ideally one of the committers being the project lead).
 +
# After the release has been announced on the mailing list and [http://planetorion.org/news/ planetorion], new and noteworthy blog posts are created for each area (tools, client, etc).
 +
 +
== Past releases ==
 +
* [https://projects.eclipse.org/projects/ecd.orion/releases/13.0 13.0 Release]
 +
* [https://projects.eclipse.org/projects/ecd.orion/releases/12.0 12.0 Release]
 +
* [https://projects.eclipse.org/projects/ecd.orion/releases/11.0 11.0 Release]
 +
* [https://projects.eclipse.org/projects/ecd.orion/releases/10.0 10.0 Release]
 +
* [https://projects.eclipse.org/projects/eclipse.orion/releases/9.0 9.0 Release]
 +
* [https://projects.eclipse.org/projects/eclipse.orion/releases/8.0 8.0 Release]
 +
* [https://projects.eclipse.org/projects/eclipse.orion/releases/7.0 7.0 Release]
 +
* [https://projects.eclipse.org/projects/eclipse.orion/releases/6.0.0 6.0 Release]
 +
* [https://projects.eclipse.org/projects/eclipse.orion/releases/5.0.0 5.0 Release]
 +
* [http://projects.eclipse.org/projects/eclipse.orion/releases/4.0.0 4.0 Release]
 
* [[Orion/Plan/3.0| 3.0 Release planning]]
 
* [[Orion/Plan/3.0| 3.0 Release planning]]
 
* [http://eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/orion/plans/orion-project-plan-3-0.xml Orion 3.0 Release Plan]
 
* [http://eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/orion/plans/orion-project-plan-3-0.xml Orion 3.0 Release Plan]
Line 14: Line 39:
 
* [[Orion/Plan/0.2| June 2011 0.2 Release Plan]]
 
* [[Orion/Plan/0.2| June 2011 0.2 Release Plan]]
 
* [[Orion/Milestone_Plan]]
 
* [[Orion/Milestone_Plan]]
 +
 +
[[Category:Orion]]

Latest revision as of 15:17, 30 November 2016

Current and future releases

Release Wind-down

As the development cycle gets closer to the release date, there is a general process we follow to ensure a successful and stable release.

When development reaches the final thirty days before release, two important steps begin the wind-down:

  1. The IP log is submitted. Before the logs are submitted, all outstanding dependencies must be checked and a decision made if they will appear in the upcoming release.
  2. A release review must be scheduled. This is done from the project page under a specific release.


During the last thirty days, development follows a different schedule. To make sure we do not introduce any regressions right before the release, we do the following:

  1. Keep working as usual for the first week of the wind-down. Typically no new features will be added at this time unless approved by the project lead
  2. Once the release review is complete (typically by the second week of the wind-down), development changes to the "last chance" stage to put in changes (with no new features), with each change requiring a +1 from one other committer. This continues for the next two weeks.
  3. The last week is reserved strictly for testing and making critical fixes, with any fix requiring a +1 from two committers (ideally one of the committers being the project lead).
  4. After the release has been announced on the mailing list and planetorion, new and noteworthy blog posts are created for each area (tools, client, etc).

Past releases