Initial forests for JDK 9
anthony.petrov at oracle.com
Fri Dec 13 04:22:28 PST 2013
On 12/13/2013 04:02 AM, mark.reinhold at oracle.com wrote:
> 2013/12/12 7:27 -0800, jonathan.gibbons at oracle.com:
>> On 12/12/2013 07:35 AM, mark.reinhold at oracle.com wrote:
>>> I think the master forest is the exception. Everyone working on the
>>> release should be aware of changes to the master, so notifications
>>> for that forest should go to jdk9-dev, just as notifications for the
>>> JDK 8 master went to jdk8-dev.
>> I question why most folk working on the release should be aware of
>> what is going on in the master. Most folk working on the release will
>> be integrating up through the dev forest, so that is the forest that
>> folk should be concerned about. If in this new world the master is just
>> going to be a time-delayed, better tested, cache of the dev forest, then
>> most folk will already be aware of the changes that have gone in.
> Hmm. Fair point. This is a new world -- or at least we're trying to
> make it so.
>> Rather than sending messages to jdk9-dev, how about setting up
>> jdk9-changes as a new alias, initially populated with the contents of
>> the jdk9-dev alias, but allowing people to opt-in or opt-out of those
>> messages as they choose, rather than always sending potentially unwanted
>> messages such that they then have to go to the trouble of filtering out.
> Okay. How about we modify Iris's original proposal as follows:
> jdk9-changes Changes to the JDK 9 master forest
> jdk9-all-changes Changes to all JDK 9 forests (including master)
> Change notifications for the master will only go to these two lists,
> and specifically not to jdk9-dev.
> To keep things simple, all of these lists will be opt-in.
> - Mark
More information about the jdk9-dev