Interaction with the CCC Process (original) (raw)
Dalibor Topic dalibor.topic at oracle.com
Wed Aug 31 18:30:22 PDT 2011
- Previous message: hg: jdk7u/jdk7u-dev/jdk: 6670868: StackOverFlow with authenticated Proxy tunnels
- Next message: Push Approval Request Template posted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
here's a draft for discussion how the JDK 7 Updates Project should interact with the existing CCC process, in order to provide additional transparency around potential upcoming interface changes future releases.
The draft is open for comments until Wednesday September 7th.
cheers, dalibor topic
Interaction with the CCC process:
Preamble: JDK 7 exposes different kinds of interfaces to its users. See http://cr.openjdk.java.net/~darcy/OpenJdkDevGuide/OpenJdkDevelopersGuide.v0.777.html#kinds_of_interfaces for an introduction. Changes to those interfaces need to be carefully managed. That's done through the CCC process. This document describes how the JDK 7 Updates Project plugs into that existing process.
Rule 0: If a changeset proposed for a JDK 7 Update forest requires a specification change, directly affects an external interface, or otherwise has a compatibility impact, a CCC request MUST be initiated. Unless special circumstances hold, a specification change to a java.* or javax.* API is out of bounds for a JDK 7 update release.
Rule 1: Currently, if the developer is not employed by Oracle, the CCC request SHOULD be initiated by the Technical Lead. Otherwise, the CCC request MUST be initiated by the developer proposing the changeset.
Rule 2: When a CCC request is initiated, the initiator MUST post that a request has been initiated on the jdk7u-dev at openjdk.java.net mailing list.
Rule 3: While a CCC request is in progress, the initiator MUST keep the jdk7u-dev at openjdk.java.net mailing list up to date on its progress, in particular whether the request has been approved.
Rule 4: As a special exception, CCC requests for changes not going into a public JDK 7 Update forest are not covered by Rule 2 and Rule 3.
Rule 5: A changeset for which the CCC request has not been approved (yet), MUST not be committed into a JDK 7 Update forest.
Rule 6: The maintainer MAY request a CCC request to be initiated for a changeset.
-- Oracle <http://www.oracle.com> Dalibor Topic | Java F/OSS Ambassador Phone: +494023646738 tel:+494023646738 | Mobile: +491772664192 tel:+491772664192 Oracle Java Platform Group
ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg
ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
- Previous message: hg: jdk7u/jdk7u-dev/jdk: 6670868: StackOverFlow with authenticated Proxy tunnels
- Next message: Push Approval Request Template posted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]