Initial forests for JDK 9 (original) (raw)
Joe Darcy joe.darcy at oracle.com
Tue Dec 10 14:09:59 PST 2013
- Previous message: Initial forests for JDK 9
- Next message: Initial forests for JDK 9
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/09/2013 10:57 PM, Iris Clark wrote:
Hi.
I'll be creating the JDK 9 forests on Thursday. I'm assuming that configuration should be the obvious extensions of what we have now for the JDK 8 Master and team forests (e.g. same jcheck settings, s/8/9/g ). One change I'd like to propose is modification of the destinations for push notifications. For JDK 8, changes to the Master and all team forests are sent to jdk8-changes at ojn. Push notifications to team forests are also sent to various -dev mailing lists. In some cases notifications may be sent to multiple mailing lists. For instance, changes to the tl forest are sent to compiler-dev, core-libs-dev, serviceability-dev, security-dev, and net-dev. With the reduction in the number of team repos in JDK 9 particularly for client, the number of duplicate push notifications will increase. I recommend that each of the forests send push notifications to new mailing lists which use the following naming convention: jdk9-forest?-changes at ojn . Notifications for jdk9 would be sent to jdk9-changes, dev to jdk9-dev-changes, hotspot-rt to jdk9-hotspot-rt-changes, etc.
That sounds like a good change to me; I think using option 1) for opt-in would be fine.
-Joe
- Previous message: Initial forests for JDK 9
- Next message: Initial forests for JDK 9
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]