webrevs.2 for macosx changes to jdk7u-osx

[Weijun Wang]

Yes, I think jdk7u-osx is only a temporary playground. There is no need 
for approval to push anything there.

In fact, it's even not as formal as jdk8/tl, where code reviews must be 
done seriously, jcheck rules must be obeyed, and all changesets will be 
pushed to the main repo with no change. The jdk7u-osx is more like 
jigsaw, the developers have their own rules, and when they finally 
integrate any change to the main repo, most likely a (or several) new 
consolidated changeset will be created.

-Max


On 12/02/2011 05:53 PM, Alan Bateman wrote:
> On 01/12/2011 21:38, Dalibor Topic wrote:
>> :
>> 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.
>>
> Dalibor - are you sure about this? I thought jdk7u/jdk7u-osx was to
> operate similar to an integration forest such as jdk8/tl so that we
> could bug fix and get the port completed before seeking permission to
> push it up to jdk7u/jdk7u. In that context I don't think it should be
> necessary to seeking approvals, other than the usual code review.
>
> -Alan