Good materials in your reply John ! So your advice is to track work groups to know better about changes in trunk of various JDK7 components.
Thanks again Le 4 avr. 2011 à 20:39, John Rose <john.r.r...@oracle.com> a écrit : > Thanks, Dalibor. > > Here's another reference: > http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-March/002665.html > > For those on lists who might not know, let me explain some of the software > development physics of OpenJDK and JDK7 in particular. > > The JDK7 engineering release process requires 1-2 weeks from the time an > engineer commits a change to the time it appears as a nicely tested download, > usable with Solaris, Windows, and Linux. Given the amount of testing and > integration done, it is remarkable achievement that this happens regularly > (about 136 times so far). > > Because we are an open-source project, as soon as an engineer commits a > change, it is visible publicly and globally. (Note that any such commit is > preceded by development, testing, and formal peer review; that's why you see > "review request" emails flying around.) The change appears first in a group > work area (jdk7/hotspot-comp for me), where it "soaks" for nightly testing of > various sorts. Periodically, changes which have accumulated in the group > area are collected in another staging area (jdk7/hotspot), where additional > testing is done by more engineers, followed by a grand push to the master > repository (jdk7/jdk7). This grand push happens as release engineers > fabricate and checked the downloads everybody sees. > > As soon as a change appears globally (in any repository), other projects, > such as the bsd and macos ports, can pick up the changes, if they dare. But > they are wise to wait for them to move up to the master (jdk7/jdk7). Pulling > those changes requires some manual merging and checking. > > Therefore, the uptake from the OpenJDK master to various porting projects is > not, and cannot be, instantaneous. In fact, if there are problems, the > process may take weeks of additional time. Because this is an open source > community, there is an direct way to improve this process: Volunteer to join > the porting projects. > > There's one more bit of the puzzle I want to point out: The OpenJDK mlvm > project has a patch repository which anticipates some of the OpenJDK7 > changes, as deltas from the bsd-port repository. There are some intrepid > souls (hi Stephen!) who build the bsd-port with these patches. When it > works, this provides a bleeding-edge preview of some new JVM features (JSR > 292, continuations, etc.). > > The bottom line is, don't expect faster-than-light travel from the porting > projects. And help them! > > Best regards, > -- John > > P.S. I am intentionally not commenting, because I don't know the details, of > how Apple and Oracle and the community are dividing the work on bsd and > macos. All I know is that intelligent people are working on keeping it sane > and making it better. > > On Apr 4, 2011, at 10:06 AM, Dalibor Topic wrote: > >> On 4/4/11 6:59 PM, Henri Gomez wrote: >>> Thanks :) >>> >>> I'm grabbing OS/X and trunk to have an idea why java.lang.invoke.* is >>> under java.dyn.* >> >> See bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7012648 >> >> See this post for more context: >> http://weblogs.java.net/blog/forax/archive/2011/01/08/javadyn-dead-long-live-what >> >> cheers, >> dalibor topic >> >> >> -- >> Oracle <http://www.oracle.com> >> Dalibor Topic | Java F/OSS Ambassador >> Phone: +494023646738 <tel:+494023646738> | | | Mobile: +491772664192 >> <tel:+491772664192> >> Oracle Java Platform Group >> >> ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg >> >> ORACLE Deutschland B.V. & Co. KG >> Hauptverwaltung: Riesstr. 25, D-80992 München >> Registergericht: Amtsgericht München, HRA 95603 >> >> Komplementärin: ORACLE Deutschland Verwaltung B.V. >> Rijnzathe 6, 3454PV De Meern, Niederlande >> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 >> Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven >> >> Green Oracle <http://www.oracle.com/commitment> Oracle is committed to >> developing practices and products that help protect the environment >> >
