webrevs.2 for macosx changes to jdk7u-osx
david.holmes at oracle.com
Fri Dec 2 02:03:06 UTC 2011
<Added core-libs-dev to the cc list>
On 2/12/2011 11:30 AM, Paul Hohensee wrote:
> I agree. Be a good idea to ask for review from all the affected teams.
> I _think_ core libs is the only one we missed, though.
My concern is that there are a number of platform specific changes being
made to java.* and javax.* classes (there are changes to sun.* as well
but that is less of a concern).
I would hope that we could find a way to not have to make platform
specific changes to such classes, and we need to be sure that the
proposed changes do not impact other platforms either in terms of
functionality or performance.
> On 12/1/11 8:07 PM, David Holmes wrote:
>> On 2/12/2011 7:38 AM, Dalibor Topic wrote:
>>> On 12/1/11 6:12 PM, Michael McMahon wrote:
>>>> Yes, that is correct. This push is initially just for jdk7u-osx, which
>>>> is a development forest. I'm not sure exactly what the procedure
>>>> will be yet
>>>> for the push into jdk7u-dev.
>>> There is no special procedure for pushing into jdk7u-osx that's
>>> different from
>>> the one for jdk7u-dev. You need to submit a bulk change request for
>>> approval first,
>>> someone (i.e. either me or Edvard) needs to approve it, then the push
>>> can happen
>>> - regardless whether that's jdk7u-dev or jdk7u-osx.
>> All the osx porting work is being discussed on the macosx-port-dev
>> mailing list. Most core-libs subscribers will not be on that list
>> (including me - which means my cc to that list will either bounce or
>> get held up). There are proposed changes to core Java classes that
>> should be explicitly reviewed and approved by the core-libs folk in my
More information about the core-libs-dev