JDK 7 Updates: Phase2 Process Description
Phase2 is used to describe the time during which a particular jdk7u release enters stabilization mode. A dedicated (stabilization) jdk7u$N forest is created from the jdk7u forest. Timelines are communicated on the firstname.lastname@example.org mailing list when this occurs.
Only critical bug fixes should be considered as candidates for integration into a stabilization forest. Examples may include regressions or serious functionality issues. To enable a maintainer to coordinate with all appropriate stake holders in order to ensure that a fix is appropriate for a stabilization forest, you MUST either use an appropriate mechanism to inform the appropriate stake holders of your critical fix approval request, e.g. by editing the bug in the bug database, or by working with a maintainer directly - in that case, please provide the maintainer with the following:
- CR number you are working on
- Rationale for why the fix should be approved, including the benefit and risks involved, what testing has been done, and what the results were.
Fixes cannot be integrated to a stabilization forest without receiving approval for such a "critical fix approval" request.
In conjunction with above, a phase2 push approval request also needs to be filed. See the phase2 template for more information on that.
Note that the regular 7u-dev forest remains open for fixes during the same timeframe for when a stabilization forest is open. Fixes approved for the stabilization forest are pushed to the jdk7u-dev forest by a Committer. They are integrated into the stabilization forest by a Maintainer. Fixes not destined for the stabilization forest follow the normal approval template process and upon approval, are pushed into the jdk7u-dev forest.