Initial forests for JDK 9
jonathan.gibbons at oracle.com
Thu Dec 12 15:27:16 PST 2013
On 12/12/2013 07:35 AM, mark.reinhold at oracle.com wrote:
> 2013/12/11 10:57 -0800, stuart.marks at oracle.com:
>> I wholeheartedly agree that push notifications should be moved away from the
>> various *-dev discussion lists and moved onto dedicated change notification
>> lists, per forest.
>> If the "master" forest ends up actually being called "master" per my earlier
>> e-mail then the notification list for it would be jdk9-master-changes.
> 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.
> - Mark
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.
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.
More information about the jdk9-dev