From Kelly.Ohair at Sun.COM Tue Feb 2 17:58:36 2010 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Tue, 02 Feb 2010 17:58:36 -0800 Subject: JAXP 1.4.3 Integration into JDK7 M6 Message-ID: <4B68D84C.8030809@sun.com> I will be changing the jdk7/tl/jaxp repository to use the JAXP 1.4.3 source bundle at: https://jaxp.dev.java.net/files/documents/913/147490/jdk7-jaxp-m6.zip ReleaseNotes: https://jaxp.dev.java.net/1.4/1.4.3/ReleaseNotes.html Changelog: https://jaxp.dev.java.net/1.4/1.4.3/changelog.html Currently we have 1.4.2, and I'm told 10 of the bugs in the above list are the ones we are getting with this upgrade. Questions: 1. Should we file jdk 7 SubCR's of the 10 JAXP bugs fixed in this m6 drop? 2. Should the changeset comment include all 10 of these JAXP bugs, or should I just create one CR "Upgraded to JAXP 1.4.3"? -kto From Joe.Darcy at Sun.COM Wed Feb 3 13:41:15 2010 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Wed, 03 Feb 2010 13:41:15 -0800 Subject: JAXP 1.4.3 Integration into JDK7 M6 In-Reply-To: <4B68D84C.8030809@sun.com> References: <4B68D84C.8030809@sun.com> Message-ID: <4B69ED7B.5010102@sun.com> Hello. Kelly O'Hair wrote: > > I will be changing the jdk7/tl/jaxp repository to use the JAXP 1.4.3 > source bundle at: > https://jaxp.dev.java.net/files/documents/913/147490/jdk7-jaxp-m6.zip > > ReleaseNotes: https://jaxp.dev.java.net/1.4/1.4.3/ReleaseNotes.html > Changelog: https://jaxp.dev.java.net/1.4/1.4.3/changelog.html > > Currently we have 1.4.2, and I'm told 10 of the bugs in the above list > are the ones we are getting with this upgrade. > > Questions: > 1. Should we file jdk 7 SubCR's of the 10 JAXP bugs fixed in this m6 > drop? Yes, I think this is the right approach to make bug queries easier; "Is this bug fixed in the jaxp in JDK 7? Yes, there is a subCR in JDK 7 for it." In addition, there can be a "upgrade JDK 7 to jaxp x.y.z" bug to track the changes specific to the JDK, such as updating the properties files. > 2. Should the changeset comment include all 10 of these JAXP bugs, or > should I just create one CR "Upgraded to JAXP 1.4.3"? I definately think there should be an "Upgraded to JAXP 1.4.3" bug in the changeset and that the bug database should have the subCRs. Listing all 10 jaxp bugs would be more informative, but a bit more work. -Joe From Joe.Darcy at Sun.COM Thu Feb 4 15:47:48 2010 From: Joe.Darcy at Sun.COM (Joe Darcy) Date: Thu, 04 Feb 2010 15:47:48 -0800 Subject: JAXP 1.4.3 Integration into JDK7 M6 In-Reply-To: <4B69ED7B.5010102@sun.com> References: <4B68D84C.8030809@sun.com> <4B69ED7B.5010102@sun.com> Message-ID: <4B6B5CA4.1060407@sun.com> Joseph D. Darcy wrote: > Hello. > > Kelly O'Hair wrote: >> >> I will be changing the jdk7/tl/jaxp repository to use the JAXP 1.4.3 >> source bundle at: >> https://jaxp.dev.java.net/files/documents/913/147490/jdk7-jaxp-m6.zip >> >> ReleaseNotes: https://jaxp.dev.java.net/1.4/1.4.3/ReleaseNotes.html >> Changelog: https://jaxp.dev.java.net/1.4/1.4.3/changelog.html >> >> Currently we have 1.4.2, and I'm told 10 of the bugs in the above list >> are the ones we are getting with this upgrade. >> >> Questions: >> 1. Should we file jdk 7 SubCR's of the 10 JAXP bugs fixed in this m6 >> drop? > > Yes, I think this is the right approach to make bug queries easier; "Is > this bug fixed in the jaxp in JDK 7? Yes, there is a subCR in JDK 7 for > it." > > In addition, there can be a "upgrade JDK 7 to jaxp x.y.z" bug to track > the changes specific to the JDK, such as updating the properties files. > >> 2. Should the changeset comment include all 10 of these JAXP bugs, or >> should I just create one CR "Upgraded to JAXP 1.4.3"? > > I definately think there should be an "Upgraded to JAXP 1.4.3" bug in > the changeset and that the bug database should have the subCRs. Listing > all 10 jaxp bugs would be more informative, but a bit more work. After some discussion with other members of the release team, in the situation where the delivered component is using the same bug system as the JDK, it is preferable to 1) Have a bug to upgrade the component in the JDK 2) Have the changset for the JDK upgrade list both the "upgrade the component" bug and the bugs being fixed by the upgrade, the 10 or so jaxp bugs in this case. -Joe From mr at sun.com Thu Feb 4 20:07:13 2010 From: mr at sun.com (Mark Reinhold) Date: Thu, 04 Feb 2010 20:07:13 -0800 Subject: JAXP 1.4.3 Integration into JDK7 M6 In-Reply-To: joe.darcy@sun.com; Thu, 04 Feb 2010 15:47:48 PST; <4B6B5CA4.1060407@sun.com> Message-ID: <20100205040713.C84AD689@eggemoggin.niobe.net> > Date: Thu, 04 Feb 2010 15:47:48 -0800 > From: joe.darcy at sun.com > ... > > After some discussion with other members of the release team, in the situation > where the delivered component is using the same bug system as the JDK, it is > preferable to > > 1) Have a bug to upgrade the component in the JDK > 2) Have the changset for the JDK upgrade list both the "upgrade the component" > bug and the bugs being fixed by the upgrade, the 10 or so jaxp bugs in this > case. Please also make sure that the upgrade bug itself lists all of the upstream bug numbers too. - Mark