See below.
On 10/10/11 3:38 PM, Dr Andrew John Hughes wrote:
On 07:42 Mon 10 Oct , Kelly O'Hair wrote:
My concern with this speeding up of the delivery of the Mac changes into jdk7u
is that the jdk7u
and jdk8 repositories were related at one point in time, but are no longer
directly related.
You cannot pull or push changesets back and forth between jdk8 and jdk7u
repositories, you can
only transplant them by re-applying patches and hope it works.
Most projects are getting changes into jdk8 first, they let them bake and
hopefully then transport the
same patch to jdk7u. As jdk8 morphs away from jdk7u, this may get more
difficult but in my
opinion is easier than the other way around.
Patches that have been accepted in jdk8, get less scrutiny as they enter jdk7u
in my opinion, because of
that bake time.
If this project works in the opposite way as all others, that could create
problems if the patches put into
jdk7u are unacceptable to jdk8 reviewers. It also skews jdk7u and jdk8 for
everyone else.
So although this may speed up this need, it may slow down many others.
I would rather see an all out effort to get these changes into jdk8 first, and
perhaps pull in the
changes incrementally into jdk7u as it progresses.
That doesn't mean you can't have such a forest to hold the jdk7u work, but
allowing it to be a development
forest without any controls on the changesets seems to open the door to the
exact same problem we have
now, where we have a MacOS port set of changes that do not work on the other 8
platforms, and whose
changesets are potentially unacceptable to the jdk8 reviewers.
If having this forest provides a place to hold vetted MacOS port changesets,
that vetting needs to include
review and acceptability into the jdk8 repositories, in which case, why can't
they be in jdk8 too.
Just my opinion.
I tend to agree with this. Moreover, do we know what testing is being done on
these OSX changes?
We plan to pass all of Oracle's test suites on currently supported platforms
before integrating into jdk7u. What subset of those test suites the OSX
port
must pass before integration into jdk7u is an open question right now. Imo,
at least the jdk7 jcks.
I'd hate to see stuff going directly into 7u which breaks or hinders other
platforms. It's
especially worrying as there's still no TCK for 7 to help catch such breakages.
A major goal of having a separate 7u-derived osx port development forest
is to
avoid pushing potentially destabilizing changes directly into 7u.
Paul
-kto
