From mr at sun.com Sun Nov 1 22:15:38 2009 From: mr at sun.com (Mark Reinhold) Date: Sun, 01 Nov 2009 22:15:38 -0800 Subject: JDK 7 M5 extended to build 76 (2009/11/12) In-Reply-To: gnu_andrew@member.fsf.org; Sun, 01 Nov 2009 15:20:25 GMT; <17c6771e0911010720w572cd963p5031e10426e5ee1d@mail.gmail.com> Message-ID: <20091102061538.8C3984FD@eggemoggin.niobe.net> > Date: Sun, 01 Nov 2009 15:20:25 +0000 > From: Andrew John Hughes > 2009/11/1 Andrew John Hughes : >> It seems that this fix: >> >> http://hg.openjdk.java.net/jdk7/build/jdk/rev/9bc5338675e0 >> >> did not make it into b75 (was build promoted in the end?) >> Can we make sure this ends up in m5 so it can actually build itself? > > Likewise, > > http://hg.openjdk.java.net/jdk7/build/jdk/rev/e2de121c27c4 > > wasn't promoted so only the HotSpot part of the Zero assembler port is there. I don't know why the build forest wasn't integrated in time for b75. I agree that it would be good to have these changes in M5. I have no objection to the pending changes in the build forest being pulled into M5 provided that (1) They're tested in the RE build environment in advance, and (2) Tim is willing to run them through the b76 integration which he'll be starting tomorrow night PST. - Mark From mr at sun.com Sun Nov 1 22:30:36 2009 From: mr at sun.com (Mark Reinhold) Date: Sun, 01 Nov 2009 22:30:36 -0800 Subject: Approval request for JAXP update in JDK7 M5 In-Reply-To: tim.bell@sun.com; Fri, 30 Oct 2009 15:49:17 PDT; <4AEB6D6D.5020008@sun.com> Message-ID: <20091102063036.BAEF44FD@eggemoggin.niobe.net> > Date: Fri, 30 Oct 2009 15:49:17 -0700 > From: tim.bell at sun.com > This request is for the following changeset to be included in M5: > > http://hg.openjdk.java.net/jdk7/tl/jaxp/rev/2f83acf616a7 > > The update is to use a newer jaxp source bundle from upstream: > https://jaxp.dev.java.net/files/documents/913/144160/jdk7-jaxp-m5.zip > > As Joe Wang mentions (see above), these changes are already in JDK6u18. > That should make the risk level low. In theory, perhaps, but there are at least two significant differences here. One is that the process of integrating JAXP into JDK 7 is now quite different from that of Sun's proprietary 6uX releases (and that's a good thing). The other is that we (i.e., Sun) do not currently have the QA resources needed to test such a change to the extent required to ensure (with high probability) that everything will be working as expected in M5. At this very late stage in M5 I'm willing to take on a certain amount of risk for brand-new features, but not for existing functionality upon which many other parts of the platform depend. > If we do nothing, this change is already in the TL forest, which means > by default it would go into M6 (probably b77). Yes. That does seem a more appropriate target. - Mark From Tim.Bell at Sun.COM Sun Nov 1 23:29:39 2009 From: Tim.Bell at Sun.COM (Tim Bell) Date: Sun, 01 Nov 2009 23:29:39 -0800 Subject: JDK 7 M5 extended to build 76 (2009/11/12) In-Reply-To: <20091102061538.8C3984FD@eggemoggin.niobe.net> References: <20091102061538.8C3984FD@eggemoggin.niobe.net> Message-ID: <4AEE8A63.1000609@sun.com> Mark Reinhold wrote: >> Date: Sun, 01 Nov 2009 15:20:25 +0000 >> From: Andrew John Hughes > >> 2009/11/1 Andrew John Hughes : >>> It seems that this fix: >>> >>> http://hg.openjdk.java.net/jdk7/build/jdk/rev/9bc5338675e0 >>> >>> did not make it into b75 (was build promoted in the end?) >>> Can we make sure this ends up in m5 so it can actually build itself? >> Likewise, >> >> http://hg.openjdk.java.net/jdk7/build/jdk/rev/e2de121c27c4 >> >> wasn't promoted so only the HotSpot part of the Zero assembler port is there. > > I don't know why the build forest wasn't integrated in time for b75. > > I agree that it would be good to have these changes in M5. So do I. Thank you, Mark. > I have no objection to the pending changes in the build forest being > pulled into M5 provided that (1) They're tested in the RE build > environment in advance, and (2) Tim is willing to run them through > the b76 integration which he'll be starting tomorrow night PST. I will put this together and get started with the first round of build/testing. I expect another cycle tomorrow (Monday) to pick up a few other changes. Tim From Tim.Bell at Sun.COM Mon Nov 2 01:14:18 2009 From: Tim.Bell at Sun.COM (Tim Bell) Date: Mon, 02 Nov 2009 01:14:18 -0800 Subject: JDK 7 M5 extended to build 76 (2009/11/12) In-Reply-To: <4AEE8A63.1000609@sun.com> References: <20091102061538.8C3984FD@eggemoggin.niobe.net> <4AEE8A63.1000609@sun.com> Message-ID: <4AEEA2EA.6070607@sun.com> > Mark Reinhold wrote: >> I have no objection to the pending changes in the build forest being >> pulled into M5 provided that (1) They're tested in the RE build >> environment in advance, and (2) Tim is willing to run them through >> the b76 integration which he'll be starting tomorrow night PST. I (Tim Bell) wrote: > I will put this together and get started with the first round of > build/testing. I expect another cycle tomorrow (Monday) to pick > up a few other changes. As we begin the day (Monday) around the world, this is what we have in the first round (test builds are still running). I expect a few more changes to arrive in the next ~20 hours.... http://cr.openjdk.java.net/~tbell/M5-open-MASTER/webrev.00/ Tim From joe.wang at sun.com Mon Nov 2 09:44:32 2009 From: joe.wang at sun.com (Joe Wang) Date: Mon, 02 Nov 2009 09:44:32 -0800 Subject: Approval request for JAXP update in JDK7 M5 In-Reply-To: <20091102063036.BAEF44FD@eggemoggin.niobe.net> References: <20091102063036.BAEF44FD@eggemoggin.niobe.net> Message-ID: <4AEF1A80.2020301@sun.com> Mark Reinhold wrote: >> Date: Fri, 30 Oct 2009 15:49:17 -0700 >> From: tim.bell at sun.com >> > > >> This request is for the following changeset to be included in M5: >> >> http://hg.openjdk.java.net/jdk7/tl/jaxp/rev/2f83acf616a7 >> >> The update is to use a newer jaxp source bundle from upstream: >> https://jaxp.dev.java.net/files/documents/913/144160/jdk7-jaxp-m5.zip >> >> As Joe Wang mentions (see above), these changes are already in JDK6u18. >> That should make the risk level low. >> > > In theory, perhaps, but there are at least two significant differences > here. One is that the process of integrating JAXP into JDK 7 is now > quite different from that of Sun's proprietary 6uX releases (and that's > a good thing). The other is that we (i.e., Sun) do not currently have > the QA resources needed to test such a change to the extent required > to ensure (with high probability) that everything will be working as > expected in M5. > > At this very late stage in M5 I'm willing to take on a certain amount > of risk for brand-new features, but not for existing functionality upon > which many other parts of the platform depend. > I wrote to Tim in a separate email and suggested that it would be helpful to do a PIT testing no matter which milestone we go into. Sorry I didn't Cc you and the alias. The QA team had agreed to help us perform PIT testing for JDK integration including 6 and 7. They've already done it a couple times for JDK6. Tim, Please send the link to a JPRT build when you have it. Thanks. >> If we do nothing, this change is already in the TL forest, which means >> by default it would go into M6 (probably b77). >> > > Yes. That does seem a more appropriate target. > Ok. --Joe > - Mark > From gnu_andrew at member.fsf.org Mon Nov 2 11:32:20 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Mon, 2 Nov 2009 19:32:20 +0000 Subject: JDK 7 M5 extended to build 76 (2009/11/12) In-Reply-To: <4AEEA2EA.6070607@sun.com> References: <20091102061538.8C3984FD@eggemoggin.niobe.net> <4AEE8A63.1000609@sun.com> <4AEEA2EA.6070607@sun.com> Message-ID: <17c6771e0911021132u61466055s5a38c3fb2d56c69b@mail.gmail.com> 2009/11/2 Tim Bell : >> Mark Reinhold wrote: > >>> I have no objection to the pending changes in the build forest being >>> pulled into M5 provided that (1) They're tested in the RE build >>> environment in advance, and (2) Tim is willing to run them through >>> the b76 integration which he'll be starting tomorrow night PST. > > I (Tim Bell) wrote: > >> I will put this together and get started with the first round of >> build/testing. ?I expect another cycle tomorrow (Monday) to pick >> up a few other changes. > > As we begin the day (Monday) around the world, this is what we have > in the first round (test builds are still running). I expect a few > more changes to arrive in the next ~20 hours.... > > ?http://cr.openjdk.java.net/~tbell/M5-open-MASTER/webrev.00/ > > > Tim > Thanks! Good to see the FontManager and Zero changes going in. -- Andrew :-) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Support Free Java! Contribute to GNU Classpath and the OpenJDK http://www.gnu.org/software/classpath http://openjdk.java.net PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8 From mr at sun.com Thu Nov 12 08:39:41 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 12 Nov 2009 08:39:41 -0800 Subject: Unicode 5.2.0 in JDK 7 M6 ??? In-Reply-To: yuka.kamiya@sun.com; Thu, 05 Nov 2009 22:56:04 +0900; <4AF2D974.4060509@sun.com> Message-ID: <20091112163941.DE0476F7@eggemoggin.niobe.net> > Date: Thu, 05 Nov 2009 22:56:04 +0900 > From: yuka.kamiya at sun.com > I'm looking at http://openjdk.java.net/projects/jdk7/milestones/ and > have a question about M6. > > Unicode 5.2.0 was released last month. Can we add it to JDK 7 M6? > Although the API doc for Character class needs to be updated, supporting > Unicode 5.2.0 is basically a simple data update work. Yes, please. We should always try to be up-to-date with the latest Unicode standard. - Mark From Rama.Pulavarthi at Sun.COM Mon Nov 16 16:06:01 2009 From: Rama.Pulavarthi at Sun.COM (Rama Pulavarthi) Date: Mon, 16 Nov 2009 16:06:01 -0800 Subject: Approval request for JAX-WS/JAXB 2.2 in JDK 7 M6 Message-ID: <4B01E8E9.7010109@sun.com> Hi, JAX-WS and JAXB have gone through maintenance review process recently and the latest version 2.2 (http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/index4.html) is final now. We would like to ask for approval to integrate it in JDK 7 M6. JAX-WS 2.2 adds the support for Web Services Addressing 1.0 - Metadata that brings in the complete support for Web Services Addressing - 1.0. JAX-WS 2.2 RI is frozen and is part of Java EE6/GlassFish v3 release. The implementation has been throughly tested as part of the Glassfish distribution to interoperate with other stacks at various Interop events such as WS-I Basic Profile 1.2/2.0 Testing. We are working with JCP to post the final bits and TCK by December 4th. We are targeting to integrate the final bits in b80 and are currently working on the new source bundle integration process and pre-integration testing. thanks, Rama Pulavarthi