From Bradford.Wetmore at Sun.COM Mon Feb 2 05:49:24 2009 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Sun, 01 Feb 2009 21:49:24 -0800 Subject: Update on the OpenJDK Bugzilla instance. Message-ID: <49868964.4040107@sun.com> Hi all, I've recently been leading the effort to get our OpenJDK Bugzilla instance in place, and just wanted to let folks know that we're pretty close. I took some time over the last couple days to take a snapshot of what we have and what's planned for the near and somewhat longer future. The short story is that we'll begin by tracking contributions from OpenJDK developers who do not have push rights to the JDK 6 and 7 forests. The next phase will expand the system to track most if not all of the OpenJDK projects under development. The longer story is now available on the OpenJDK website: http://openjdk.java.net/groups/web/bugzilla.html One last point. Until the general system is up, you should continue to submit new bug reports through the normal channel: http://bugs.sun.com/bugdatabase/index.jsp There's still a lot of work to be done and questions to be answered, but thought you might like to see the current status and what's being planned. Thanks, Brad From gnu_andrew at member.fsf.org Tue Feb 3 00:27:38 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Tue, 3 Feb 2009 00:27:38 +0000 Subject: JDK 7 build 45 is available at the openjdk.java.net website In-Reply-To: <17c6771e0901301321h36048668l47bc677ecfb4e6b2@mail.gmail.com> References: <49833169.10904@Sun.COM> <17c6771e0901300935u1f63f4c0x3dcbd201b57d362b@mail.gmail.com> <49833CF6.40801@Sun.COM> <17c6771e0901300953k7079cb6br3a848ce19140efc@mail.gmail.com> <498367FC.7020709@sun.com> <17c6771e0901301321h36048668l47bc677ecfb4e6b2@mail.gmail.com> Message-ID: <17c6771e0902021627n3f43556ap63f4999806884bdd@mail.gmail.com> 2009/1/30 Andrew John Hughes : > 2009/1/30 Joseph D. Darcy : >> Andrew John Hughes wrote: >>> >>> 2009/1/30 : >>> >>>> >>>> On 01/30/09 09:35, Andrew John Hughes wrote: >>>> >>>> 2009/1/30 : >>>> >>>> >>>> The OpenJDK source is available at: >>>> http://hg.openjdk.java.net/jdk7/jdk7 >>>> http://hg.openjdk.java.net/jdk7/jdk7/rev/99846f001ca2 >>>> >>>> The OpenJDK source binary plugs for the promoted JDK 7 build 45 are >>>> available under the openjdk http://openjdk.java.net website under Source >>>> Code (direct link to bundles: http://download.java.net/openjdk/jdk7) >>>> >>>> Summary of changes: >>>> http://download.java.net/jdk7/changes/jdk7-b45.html >>>> >>>> >>>> -Xiomara >>>> >>>> >>>> >>>> >>>> So did nothing change? >>>> >>>> Correct -- this build can be skipped if needed. >>>> >>>> >>> >>> Then why bother exactly? >>> >>> >>>> >>>> That webpage is empty. >>>> >>>> What is the schedule now? There have been three drops in the last half >>>> of this month. >>>> >>>> >>>> We are trying to do drops on a weekly basis now. >>>> The schedule is located here: >>>> http://openjdk.java.net/projects/jdk7/builds/ >>>> >>>> >>> >>> Thanks, I really needed twice as much work... >>> >>> >> >> Some people like to get fixes in the promoted builds faster. >> >> -Joe >> >> > > Fair enough, but this empty drop along with the amount in previous > drops suggests there isn't enough to sustain such frequent drops. And > besides, it's all in the Mercurial forests anyway... > -- > Andrew :-) > > IcedTea/OpenJDK 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 > There doesn't seem to be a zip file for this either... -- Andrew :-) IcedTea/OpenJDK 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 Xiomara.Jayasena at Sun.COM Tue Feb 3 01:13:00 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara.Jayasena at Sun.COM) Date: Mon, 02 Feb 2009 17:13:00 -0800 Subject: JDK 7 build 45 is available at the openjdk.java.net website In-Reply-To: <17c6771e0902021627n3f43556ap63f4999806884bdd@mail.gmail.com> References: <49833169.10904@Sun.COM> <17c6771e0901300935u1f63f4c0x3dcbd201b57d362b@mail.gmail.com> <49833CF6.40801@Sun.COM> <17c6771e0901300953k7079cb6br3a848ce19140efc@mail.gmail.com> <498367FC.7020709@sun.com> <17c6771e0901301321h36048668l47bc677ecfb4e6b2@mail.gmail.com> <17c6771e0902021627n3f43556ap63f4999806884bdd@mail.gmail.com> Message-ID: <49879A1C.1050207@Sun.COM> On 02/02/09 16:27, Andrew John Hughes wrote: > 2009/1/30 Andrew John Hughes : > >> 2009/1/30 Joseph D. Darcy : >> >>> Andrew John Hughes wrote: >>> >>>> 2009/1/30 : >>>> >>>> >>>>> On 01/30/09 09:35, Andrew John Hughes wrote: >>>>> >>>>> 2009/1/30 : >>>>> >>>>> >>>>> The OpenJDK source is available at: >>>>> http://hg.openjdk.java.net/jdk7/jdk7 >>>>> http://hg.openjdk.java.net/jdk7/jdk7/rev/99846f001ca2 >>>>> >>>>> The OpenJDK source binary plugs for the promoted JDK 7 build 45 are >>>>> available under the openjdk http://openjdk.java.net website under Source >>>>> Code (direct link to bundles: http://download.java.net/openjdk/jdk7) >>>>> >>>>> Summary of changes: >>>>> http://download.java.net/jdk7/changes/jdk7-b45.html >>>>> >>>>> >>>>> -Xiomara >>>>> >>>>> >>>>> >>>>> >>>>> So did nothing change? >>>>> >>>>> Correct -- this build can be skipped if needed. >>>>> >>>>> >>>>> >>>> Then why bother exactly? >>>> >>>> >>>> >>>>> That webpage is empty. >>>>> >>>>> What is the schedule now? There have been three drops in the last half >>>>> of this month. >>>>> >>>>> >>>>> We are trying to do drops on a weekly basis now. >>>>> The schedule is located here: >>>>> http://openjdk.java.net/projects/jdk7/builds/ >>>>> >>>>> >>>>> >>>> Thanks, I really needed twice as much work... >>>> >>>> >>>> >>> Some people like to get fixes in the promoted builds faster. >>> >>> -Joe >>> >>> >>> >> Fair enough, but this empty drop along with the amount in previous >> drops suggests there isn't enough to sustain such frequent drops. And >> besides, it's all in the Mercurial forests anyway... >> -- >> Andrew :-) >> >> IcedTea/OpenJDK 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 >> >> > > There doesn't seem to be a zip file for this either... > Thanks for pointing that out -- fixed. -Xiomara From gnu_andrew at member.fsf.org Thu Feb 5 19:23:36 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Thu, 5 Feb 2009 19:23:36 +0000 Subject: FOSDEM: Talk Recordings Message-ID: <17c6771e0902051123q4e000d1et67ca0ec2e05b3295@mail.gmail.com> Hi all, I'll be bringing along my video camera again, all things permitting. Previous recordings can be seen on http://fuseyism.com/ Unfortunately, things so far haven't gone as I'd like. I've been unable to get hold of more tapes for recording talks, so I'll be bringing my laptop with firewire along and hoping a combination of four tapes and a hard disc will get me through... Help would be appreciated, even if it's just making sure I have some power and an unblocked view of the speaker :D It would be nice to get these online ASAP, so if you have some spare cycles during FOSDEM and want to encode one of the movies, please let me know. The originals are in DV format and I encode to three sizes of Ogg Theora (a nice little script I have will do this for you, provided you have ffmpeg2theora on your box and optionally mplayer/speex for an audio track -- see attachment). If you particularly want your talk recorded, please let me know. Alternatively, if for some reason you'd rather not have it recorded, let me know as well. Thanks, and see you all at FOSDEM, -- Andrew :-) IcedTea/OpenJDK 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 Xiomara.Jayasena at Sun.COM Fri Feb 6 06:15:48 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Thu, 05 Feb 2009 22:15:48 -0800 Subject: JDK 7 build 46 is available at the openjdk.java.net website Message-ID: <498BD594.90903@sun.com> The OpenJDK source is available at: http://hg.openjdk.java.net/jdk7/jdk7 http://hg.openjdk.java.net/jdk7/jdk7/rev/e8a2a4d18777 The OpenJDK source binary plugs for the promoted JDK 7 build 46 are available under the openjdk http://openjdk.java.net website under Source Code (direct link to bundles: http://download.java.net/openjdk/jdk7) Summary of changes: http://download.java.net/jdk7/changes/jdk7-b46.html -Xiomara From martinrb at google.com Fri Feb 6 09:05:56 2009 From: martinrb at google.com (Martin Buchholz) Date: Fri, 6 Feb 2009 01:05:56 -0800 Subject: JDK 7 build 46 is available at the openjdk.java.net website In-Reply-To: <498BD594.90903@sun.com> References: <498BD594.90903@sun.com> Message-ID: <1ccfd1c10902060105u25ea6528q6a033e5670a37dd3@mail.gmail.com> Hi Xiomara, Please forward the following bug reports to whomever might fix them. The summary of changes script has the bug that it reports all classes_util_i18n twice, since they are also reported under classes_util. Probably the script is doing substring or regex matching when it should be testing subcategory string equality. If I look at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6764308 it says "Reported against b03" which is ambiguous, and doesn't give any "Release Fixed". On the other hand, http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6756569 says the mysterious "Release Fixed , 6-open(b13)" Where is jdk7? Is there supposed to be something before the comma?! Martin On Thu, Feb 5, 2009 at 22:15, Xiomara Jayasena wrote: > > > The OpenJDK source is available at: > http://hg.openjdk.java.net/jdk7/jdk7 > http://hg.openjdk.java.net/jdk7/jdk7/rev/e8a2a4d18777 > > The OpenJDK source binary plugs for the promoted JDK 7 build 46 are > available under the openjdk http://openjdk.java.net website under Source > Code (direct link to bundles: http://download.java.net/openjdk/jdk7) > > Summary of changes: > http://download.java.net/jdk7/changes/jdk7-b46.html > > > -Xiomara > > From Xiomara.Jayasena at Sun.COM Fri Feb 6 09:21:38 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Fri, 06 Feb 2009 01:21:38 -0800 Subject: JDK 7 build 46 is available at the openjdk.java.net website In-Reply-To: <1ccfd1c10902060105u25ea6528q6a033e5670a37dd3@mail.gmail.com> References: <498BD594.90903@sun.com> <1ccfd1c10902060105u25ea6528q6a033e5670a37dd3@mail.gmail.com> Message-ID: <498C0122.1000909@sun.com> Hi Martin, Hope all is well with you. Yes, I'll forward the reports -- Thank you for sending these. -Xiomara Martin Buchholz wrote: > Hi Xiomara, > > Please forward the following bug reports to whomever > might fix them. > > The summary of changes script has the bug that > it reports all classes_util_i18n twice, since they are > also reported under classes_util. > Probably the script is doing substring or regex matching > when it should be testing subcategory string equality. > > If I look at > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6764308 > it says "Reported against b03" which is ambiguous, > and doesn't give any "Release Fixed". > > On the other hand, > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6756569 > says the mysterious > "Release Fixed , 6-open(b13)" > Where is jdk7? Is there supposed to be something before the comma?! > > Martin > > On Thu, Feb 5, 2009 at 22:15, Xiomara Jayasena wrote: > >> The OpenJDK source is available at: >> http://hg.openjdk.java.net/jdk7/jdk7 >> http://hg.openjdk.java.net/jdk7/jdk7/rev/e8a2a4d18777 >> >> The OpenJDK source binary plugs for the promoted JDK 7 build 46 are >> available under the openjdk http://openjdk.java.net website under Source >> Code (direct link to bundles: http://download.java.net/openjdk/jdk7) >> >> Summary of changes: >> http://download.java.net/jdk7/changes/jdk7-b46.html >> >> >> -Xiomara >> >> >> From mark at klomp.org Wed Feb 11 08:21:15 2009 From: mark at klomp.org (Mark Wielaard) Date: Wed, 11 Feb 2009 09:21:15 +0100 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <498D183D.8040104@sun.com> References: <498D183D.8040104@sun.com> Message-ID: <1234340475.2340.13.camel@fedora.wildebeest.org> Hi Brad, On Fri, 2009-02-06 at 21:12 -0800, Brad Wetmore wrote: > As I posted on the discuss list earlier this week [1], I have set up an > instance of Bugzilla for use by the various OpenJDK efforts. > > The system is now live. Please see the project page at: > > http://openjdk.java.net/groups/web/bugzilla.html > > for general notes, instructions, and the URL. > > I've made an initial pass at configuration with feedback from several > folks, but I know we will continue tuning this system to best fit our needs. Thanks for setting this up. A quick question before I start using this. It says "Please review the Terms of Use". This is the first bugzilla instance I know that comes with a four page legal requirements document before usage. I started printing them out and reviewing them as requested but they seem somewhat odd. They require signing over rights to Collabnet, O'Reilly and Sun of any source code posted, can be changed at any time without notice, so you will have to review them each time you file a new bug, and any legal disputes need to be fought in a foreign country at the other side of the world. They all seem a bit out of place for the OpenJDK community usage, I suspect they were copy/pasted from some unrelated project. Can we get rid of them? Thanks, Mark From gnu_andrew at member.fsf.org Wed Feb 11 17:46:42 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Wed, 11 Feb 2009 17:46:42 +0000 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <1234340475.2340.13.camel@fedora.wildebeest.org> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> Message-ID: <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> 2009/2/11 Mark Wielaard : > Hi Brad, > > On Fri, 2009-02-06 at 21:12 -0800, Brad Wetmore wrote: >> As I posted on the discuss list earlier this week [1], I have set up an >> instance of Bugzilla for use by the various OpenJDK efforts. >> >> The system is now live. Please see the project page at: >> >> http://openjdk.java.net/groups/web/bugzilla.html >> >> for general notes, instructions, and the URL. >> >> I've made an initial pass at configuration with feedback from several >> folks, but I know we will continue tuning this system to best fit our needs. > > Thanks for setting this up. A quick question before I start using this. > > It says "Please review the Terms of Use". This is the first bugzilla > instance I know that comes with a four page legal requirements document > before usage. I started printing them out and reviewing them as > requested but they seem somewhat odd. They require signing over rights > to Collabnet, O'Reilly and Sun of any source code posted, can be changed > at any time without notice, so you will have to review them each time > you file a new bug, and any legal disputes need to be fought in a > foreign country at the other side of the world. They all seem a bit out > of place for the OpenJDK community usage, I suspect they were > copy/pasted from some unrelated project. Can we get rid of them? > > Thanks, > > Mark > > +1 Applying the java.net terms of use wholesale and without alteration to the unrelated OpenJDK project seems very odd. We already have the GPL for licensing the project and the SCA to handle contributions. These terms of use go far beyond 'Users uploading inappropriate materials' and I don't see why we are handing any rights over to OReilly or Collab who have nothing to do with the OpenJDK project. -- 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 davidh at 7gen.com Wed Feb 11 19:48:47 2009 From: davidh at 7gen.com (David Herron) Date: Wed, 11 Feb 2009 11:48:47 -0800 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> Message-ID: <49932B9F.10908@7gen.com> Andrew John Hughes wrote: > 2009/2/11 Mark Wielaard : > >> Hi Brad, >> >> On Fri, 2009-02-06 at 21:12 -0800, Brad Wetmore wrote: >> >>> As I posted on the discuss list earlier this week [1], I have set up an >>> instance of Bugzilla for use by the various OpenJDK efforts. >>> >>> The system is now live. Please see the project page at: >>> >>> http://openjdk.java.net/groups/web/bugzilla.html >>> >>> for general notes, instructions, and the URL. >>> >>> I've made an initial pass at configuration with feedback from several >>> folks, but I know we will continue tuning this system to best fit our needs. >>> >> Thanks for setting this up. A quick question before I start using this. >> >> It says "Please review the Terms of Use". This is the first bugzilla >> instance I know that comes with a four page legal requirements document >> before usage. I started printing them out and reviewing them as >> requested but they seem somewhat odd. They require signing over rights >> to Collabnet, O'Reilly and Sun of any source code posted, can be changed >> at any time without notice, so you will have to review them each time >> you file a new bug, and any legal disputes need to be fought in a >> foreign country at the other side of the world. They all seem a bit out >> of place for the OpenJDK community usage, I suspect they were >> copy/pasted from some unrelated project. Can we get rid of them? >> >> Thanks, >> >> Mark >> >> >> > > +1 > > Applying the java.net terms of use wholesale and without alteration to > the unrelated OpenJDK project seems very odd. We already have the GPL > for licensing the project and the SCA to handle contributions. These > terms of use go far beyond 'Users uploading inappropriate materials' > and I don't see why we are handing any rights over to OReilly or > Collab who have nothing to do with the OpenJDK project. > +1 I understand that Sun has a requirement to have privacy policies and other legalisms. Some kind of terms of use agreement is going to be required. Most collaborative websites have terms of use requirements. Since openjdk.java.net is not administered by CollabNet, it seems that reusing the java.net terms of use (which involves CollabNet) on a sub-site that isn't administered by CollabNet feels odd. There is at least one value for rights assignment of posted source code. It's the ability to convert a unit test posted in a bug report into an official unit test in the source tree. There was an idea I started to work on a couple months ago, while still a Sun employee, to make a similar terms of use change for bugs.sun.com bugs. The bugs.sun.com terms of use does not allow reuse of posted source code for other purposes. Sometimes the code a bug reportee posts in their bug report is a useful valid unit test and it would be cool to repurpose that code into a normal unit test. But just like any other source code submission, Sun's policy is it requires rights assignment for copyright sharing. e.g. that's the purpose of the SCA, right? But if the bug submissions place, whether it's bugs.sun.com or bugs.openjdk.java.net, doesn't have copyright assignment then by Sun's policies as I understand them the source cannot be reused in other places. I'd chatted with the Sun manager who oversees the bugs.sun.com process, he liked the idea, but neither of us had time to take it further. - David Herron From gnu_andrew at member.fsf.org Wed Feb 11 20:09:48 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Wed, 11 Feb 2009 20:09:48 +0000 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <49932B9F.10908@7gen.com> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> <49932B9F.10908@7gen.com> Message-ID: <17c6771e0902111209r468d81fbue02e78bed8380b56@mail.gmail.com> 2009/2/11 David Herron : > Andrew John Hughes wrote: > > 2009/2/11 Mark Wielaard : > > > Hi Brad, > > On Fri, 2009-02-06 at 21:12 -0800, Brad Wetmore wrote: > > > As I posted on the discuss list earlier this week [1], I have set up an > instance of Bugzilla for use by the various OpenJDK efforts. > > The system is now live. Please see the project page at: > > http://openjdk.java.net/groups/web/bugzilla.html > > for general notes, instructions, and the URL. > > I've made an initial pass at configuration with feedback from several > folks, but I know we will continue tuning this system to best fit our needs. > > > Thanks for setting this up. A quick question before I start using this. > > It says "Please review the Terms of Use". This is the first bugzilla > instance I know that comes with a four page legal requirements document > before usage. I started printing them out and reviewing them as > requested but they seem somewhat odd. They require signing over rights > to Collabnet, O'Reilly and Sun of any source code posted, can be changed > at any time without notice, so you will have to review them each time > you file a new bug, and any legal disputes need to be fought in a > foreign country at the other side of the world. They all seem a bit out > of place for the OpenJDK community usage, I suspect they were > copy/pasted from some unrelated project. Can we get rid of them? > > Thanks, > > Mark > > > > > +1 > > Applying the java.net terms of use wholesale and without alteration to > the unrelated OpenJDK project seems very odd. We already have the GPL > for licensing the project and the SCA to handle contributions. These > terms of use go far beyond 'Users uploading inappropriate materials' > and I don't see why we are handing any rights over to OReilly or > Collab who have nothing to do with the OpenJDK project. > > > +1 > > I understand that Sun has a requirement to have privacy policies and other > legalisms. Some kind of terms of use agreement is going to be required. > Most collaborative websites have terms of use requirements. > > Since openjdk.java.net is not administered by CollabNet, it seems that > reusing the java.net terms of use (which involves CollabNet) on a sub-site > that isn't administered by CollabNet feels odd. > > There is at least one value for rights assignment of posted source code. > It's the ability to convert a unit test posted in a bug report into an > official unit test in the source tree. > > There was an idea I started to work on a couple months ago, while still a > Sun employee, to make a similar terms of use change for bugs.sun.com bugs. > The bugs.sun.com terms of use does not allow reuse of posted source code for > other purposes. Sometimes the code a bug reportee posts in their bug report > is a useful valid unit test and it would be cool to repurpose that code into > a normal unit test. But just like any other source code submission, Sun's > policy is it requires rights assignment for copyright sharing. e.g. that's > the purpose of the SCA, right? But if the bug submissions place, whether > it's bugs.sun.com or bugs.openjdk.java.net, doesn't have copyright > assignment then by Sun's policies as I understand them the source cannot be > reused in other places. I'd chatted with the Sun manager who oversees the > bugs.sun.com process, he liked the idea, but neither of us had time to take > it further. > > - David Herron > > > > Ok I only just noticed this and I don't know how binding they are but: http://mail.openjdk.java.net/mailman/listinfo links to the same terms of use. So do O'Reilly now own all the patches posted to the lists? I don't see how any of use ever signified our compliance with these terms. -- 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 Dalibor.Topic at Sun.COM Wed Feb 11 22:04:29 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Wed, 11 Feb 2009 23:04:29 +0100 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <17c6771e0902111209r468d81fbue02e78bed8380b56@mail.gmail.com> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> <49932B9F.10908@7gen.com> <17c6771e0902111209r468d81fbue02e78bed8380b56@mail.gmail.com> Message-ID: <49934B6D.4050702@sun.com> Andrew John Hughes wrote: > Ok I only just noticed this and I don't know how binding they are but: > > http://mail.openjdk.java.net/mailman/listinfo > > links to the same terms of use. All websites I know that are hosted under java.net (not very many, I admit) use the same terms of service, I think. That's typically how terms of use work, in my experience - unless there is a specific need for a sub-site to differ in their terms of use from their parent, they reuse the parent one. I guess what makes the OpenJDK web site different from some other free software collaboration web sites is that the OpenJDK web sites have an explicit link to the terms of use, rather then assuming the users will know where to go looking for them. That's a good thing, in my opinion. > So do O'Reilly now own all the > patches posted to the lists? I don't see how any of use ever > signified our compliance with these terms. > I don't see anything about actually transferring ownership of patches posted to lists to O'Reilly in the java.net terms of use, but then I am not a lawyer and I'm really bad at playing one ... Typically, web sites for collaboration around open source projects have terms of service associated with them, that grant the hosts of the site a broad license to contributions made to the projects regardless of the medium those contributions come through. Red Hat, for example, has their terms of use for their websites located at http://www.redhat.com/legal/legal_statement.html and they say "Rights in Content By displaying, publishing and making available for download and use by others any content, messages, text, files, images, photos, video, sounds, profiles, works of authorship, or any other materials ("Content") you give Red Hat a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through the web site. You agree that this license includes a right for Red Hat to make such Content available to other companies, organizations or individuals with whom Red Hat has relationships for the provision of services, and to use such Content in connection with the provision of those services. You understand that Red Hat may (a) transmit or distribute your Content over various public networks and in various media; and (b) make such changes to your Content as are necessary to conform and adapt that Content to the technical requirements of connecting networks, devices, services or media. You agree that this license shall permit Red Hat to take these actions. You confirm and warrant to Red Hat that you have all the rights, power and authority necessary to grant the above license." Those terms seem to me, personally, to be quite similar to those of the java.net web site, except that Red Hat hosts their web sites alone, as far as I can tell, while java.net is hosted by Sun, O'Reilly and Collab.net. Similar terms exist for the OpenSUSE, Launchpad, Sourceforge, java.net, Google Code and many other similar sites. The Eclipse foundation, for example, also points out their (pretty similar in those aspects Mark Wielaard found odd) website's terms of use on their mail subcription site at http://www.eclipse.org/mail/ . And so on. I think David explained nicely why having terms of use contain liberal grants of rights to hosts makes sense in general - it eliminates a whole class of problems that otherwise come up when reasonable people disagree what 'common sense' really means, by substituting the deceptively subjective definition of common sense for more explicit terms. Of course, that also invites a whole other class of linguistic (lawyerese vs. regular English) and 'IANAL, but ...' problems, but those kinds of misunderstandings are easier to fix then 'common sense' ones, as my favorite xkcd comic at http://xkcd.com/386/ nicely explains. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From Weijun.Wang at Sun.COM Thu Feb 12 01:27:05 2009 From: Weijun.Wang at Sun.COM (Weijun Wang) Date: Thu, 12 Feb 2009 09:27:05 +0800 Subject: Can I see what changesets comes from which which repo? Message-ID: <49937AE9.9030406@sun.com> Hi All I guess this question is not rational since Mercurial is a distributed SCM system, but I would be very glad to find out where the origin of a changeset is, at least if the changeset is directly push into this repo or pulled from another one. For example, When I look at http://hg.openjdk.java.net/jdk7/tl/jdk/, I would like to see which changesets are really tl-related. Forgive me if the question is too stupid. Thanks Max From Kelly.Ohair at Sun.COM Thu Feb 12 01:41:23 2009 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Wed, 11 Feb 2009 17:41:23 -0800 Subject: Can I see what changesets comes from which which repo? In-Reply-To: <49937AE9.9030406@sun.com> References: <49937AE9.9030406@sun.com> Message-ID: <49937E43.2020401@sun.com> Not a stupid question at all. The recording of the push/pull events is not done by Mercurial. Currently there is the email that is sent out in the form of notifications, but even knowing who pushed a changeset might not tell you the push/pull travel history of a changeset and who was involved in those pushes and pulls. It's of course the author of the changeset and the change itself that is most important, and we have that, but I understand what you are saying and I don't have a good answer. If every changeset had a passport so we know where it's been and how it got there, that would be interesting, just not sure how it could be done. If you want to know what changesets impact certain files, the 'hg log -k filename' might help. -kto Weijun Wang wrote: > Hi All > > I guess this question is not rational since Mercurial is a distributed > SCM system, but I would be very glad to find out where the origin of a > changeset is, at least if the changeset is directly push into this repo > or pulled from another one. > > For example, > > When I look at http://hg.openjdk.java.net/jdk7/tl/jdk/, I would like to > see which changesets are really tl-related. > > Forgive me if the question is too stupid. > > Thanks > Max From mark at klomp.org Thu Feb 12 08:35:34 2009 From: mark at klomp.org (Mark Wielaard) Date: Thu, 12 Feb 2009 09:35:34 +0100 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <49934B6D.4050702@sun.com> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> <49932B9F.10908@7gen.com> <17c6771e0902111209r468d81fbue02e78bed8380b56@mail.gmail.com> <49934B6D.4050702@sun.com> Message-ID: <1234427734.2271.23.camel@fedora.wildebeest.org> Hi Dalibor, On Wed, 2009-02-11 at 23:04 +0100, Dalibor Topic wrote: > All websites I know that are hosted under java.net (not very many, I > admit) use the same terms of service, I think. > That's typically how terms of use work, in my experience - unless there > is a specific need for a sub-site to differ > in their terms of use from their parent, they reuse the parent one. It indeed seems not very appropriate here seeing that our community processes are different from the general java.net ones imho. > I don't see anything about actually transferring ownership of patches > posted to lists to O'Reilly in the java.net terms of use, but then > I am not a lawyer and I'm really bad at playing one ... Precisely. There are multiple pages of legalese, so of course it is hard to find the specifics, especially since they seem not tailored to our project. But look under the section about Source Code in these terms to see the rights transfers that this agreement insists on. But specifics of the legal requirements might be irrelevant since they seem to have been copy/pasted from somewhere that wasn't created to cover our works. Lets make sure they are relevant first. > Typically, web sites for collaboration around open source projects have > terms of service associated with them, that grant > the hosts of the site a broad license to contributions made to the > projects regardless of the medium those contributions come through. Personally I have never seen that before for any of the projects I have been involved with. > Red Hat, for example, has their terms of use for their websites For corporate users, but don't use those for their community sites like sources.redhat.com, fedoraproject or their bugzilla sites. > Similar terms exist for the OpenSUSE, Launchpad, [...] A quick look suggest that they aren't as broad as the ones the openjdk bugzilla site uses but much more specific for the use cases they were designed to cover. Also, someone else might also get this wrong, but that doesn't mean we have to copy that. > it eliminates a whole class of problems that otherwise > come up when reasonable people disagree what 'common sense' really > means, by substituting the deceptively subjective definition of common > sense for more explicit terms. > > Of course, that also invites a whole other class of linguistic > (lawyerese vs. regular English) and 'IANAL, but ...' problems, but those > kinds of misunderstandings are easier to fix then 'common sense' ones, > as my favorite xkcd comic at http://xkcd.com/386/ nicely explains. I think you are missing the point. This isn't about someone being wrong on the internet. This is about communication inside a project. When you are adding explicit legal terms that seem to not match at all with the common sense of how a community interacts then there is a artificial friction that prevents people from easily contributing and exchanging ideas. The real problem here is that these terms of use seem to imply that you can only participate in the exchange of bug discussions if you relinquish your rights up front to some arbitrary "hosts" instead of having an open exchange of ideas and politely asking for specific rights that the project might need if they want to reuse some code contributions. As others pointed out in this thread, that mechanism is already there through the GPL and if deemed necessary a specific transfer of rights to Sun through the SCA if they want to reuse some code later. So not only are these new additional terms confusing, they also seem completely unnecessary for normal interaction between the project participants. Cheers, Mark From jesse.glick at sun.com Thu Feb 12 22:59:56 2009 From: jesse.glick at sun.com (Jesse Glick) Date: Thu, 12 Feb 2009 17:59:56 -0500 Subject: Can I see what changesets comes from which which repo? In-Reply-To: <49937AE9.9030406@sun.com> References: <49937AE9.9030406@sun.com> Message-ID: Weijun Wang wrote: > When I look at http://hg.openjdk.java.net/jdk7/tl/jdk/, I would like to > see which changesets are really tl-related. If you have a clone of tl/jdk, you can use: hg out -n -l10 -M http://hg.openjdk.java.net/jdk7/jdk7/jdk/ or similar. 'hg help out' for details. From Xiomara.Jayasena at Sun.COM Fri Feb 13 06:20:03 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Thu, 12 Feb 2009 22:20:03 -0800 Subject: JDK 7 build 47 is available at the openjdk.java.net website Message-ID: <49951113.6060205@sun.com> The OpenJDK source is available at: http://hg.openjdk.java.net/jdk7/jdk7 http://hg.openjdk.java.net/jdk7/jdk7/rev/d7744e86dedc The OpenJDK source binary plugs for the promoted JDK 7 build 47 are available under the openjdk http://openjdk.java.net website under Source Code (direct link to bundles: http://download.java.net/openjdk/jdk7) Summary of changes: http://download.java.net/jdk7/changes/jdk7-b47.html -Xiomara From mark at klomp.org Fri Feb 13 08:59:51 2009 From: mark at klomp.org (Mark Wielaard) Date: Fri, 13 Feb 2009 09:59:51 +0100 Subject: Some slides from the Free Java Meeting at Fosdem In-Reply-To: <1226948033.3264.68.camel@dijkstra.wildebeest.org> References: <1226948033.3264.68.camel@dijkstra.wildebeest.org> Message-ID: <1234515591.2290.25.camel@fedora.wildebeest.org> Hi all, Hope everybody recovered from the meeting. It was really fun to meet everybody and to hear about all the cool stuff people are working on. The presentations were really informative so we collected some of the presentation slides for those that couldn't make it or for those that want to go over them again. See the full list below. Dalibor linked them all from the wiki and when there are more presentations available we will add them (if you gave a presentation and also want to link to your slides please do add them or ping one of us to upload them for you): http://wiki.debian.org/Java/DevJam/2009/Fosdem Original talk abstracts and bios of the speakers can be found at: http://fosdem.org/2009/schedule/devroom/freejava Thanks for a great event! your friendly ad hoc Fosdem meeting committee, Dalibor Topic, Andrew John Hughes, Andrew Haley, David Herron and Mark Wielaard Presentations Free Java Meeting, Fosdem: Caciocavallo, Roman Kennke & Mario Torre http://www.limasoftware.net/neugens/downloads/classpath/caciocavallo/Cacio_Presentation_2.pdf XRender Java2D Pipeline, Clemens Eisserer http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Clemens-XRender.odp Gervill Software Synthesizer, Karl Helgason https://gervill.dev.java.net/files/documents/7973/126418/fosdem2009-gervill.pdf Cacao, Michael Starzinger http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Michael-Cacao.pdf VMKit, Nicolas Geoffray http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Nicolas-VMKit.pdf Groovy Grails for NetBeans, Matthias Schmidt http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Matthias-Groovy-Tooling.pdf Towards a Universal VM, Alex Buckley http://blogs.sun.com/abuckley/resource/FOSDEM2009-TowardsAUniversalVM.pdf JSR292 - Supporting Dynamically Typed Languages, Remi Forax http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Remi-JSR292.pdf JamVM, Robert Lougher http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Robert-JamVM.pdf JNode, Peter Barth http://wiki.debian.org/Java/DevJam/2009/Fosdem?action=AttachFile&do=get&target=Peter-JNode.pdf Zero/Shark, Gary Benson http://gbenson.net/wp-content/uploads/2009/02/fosdem-2009.pdf From flyingimmi at live.de Fri Feb 13 10:20:05 2009 From: flyingimmi at live.de (Flyingimmi) Date: Fri, 13 Feb 2009 02:20:05 -0800 (PST) Subject: Read numbers from java window Message-ID: <21982814.post@talk.nabble.com> Hello all, I'm trying to read continuously updated numbers from a java window. ( I don't have the source code for the program) I was already able to do this using a custom OCR algorithm but this is a bit slow and too error-prone. Second I tried to find the memory address where the most recent value was stored and simply checked the same memory address over and over again. This work as well to some extend , after a changing period of time the new values where stored a different location and I was not able to get access to the updated values anymore. I can only suspect was happened but I guess some kind of memory allocation. ( I was using the Sun Java Runtime on Ubuntu 8.10 ) Since all my ideas failed so far, I'm curious if there is a chance to read number ( or characters ) from a java window if I use OpenJDK. Any hint suggesting where I can find information for this task a very much appreciated. best regards flyingimmi -- View this message in context: http://www.nabble.com/Read-numbers-from-java-window-tp21982814p21982814.html Sent from the OpenJDK General discussion mailing list archive at Nabble.com. From allenfans at gmail.com Fri Feb 13 10:50:23 2009 From: allenfans at gmail.com (Allen) Date: Fri, 13 Feb 2009 21:50:23 +1100 Subject: Read numbers from java window In-Reply-To: <21982814.post@talk.nabble.com> References: <21982814.post@talk.nabble.com> Message-ID: What is a java window ? Thanks On Fri, Feb 13, 2009 at 9:20 PM, Flyingimmi wrote: > > Hello all, > > I'm trying to read continuously updated numbers from a java window. ( I > don't have the source code for the program) > > I was already able to do this using a custom OCR algorithm but this is a > bit slow and too error-prone. > > Second I tried to find the memory address where the most recent value was > stored and simply checked the > same memory address over and over again. This work as well to some extend , > after a changing period of time the new > values where stored a different location and I was not able to get access > to > the updated values anymore. I can only suspect was happened but I guess > some > kind of memory allocation. ( I was using the Sun Java Runtime on Ubuntu > 8.10 > ) > > Since all my ideas failed so far, I'm curious if there is a chance to read > number ( or characters ) from a java window > if I use OpenJDK. Any hint suggesting where I can find information for this > task a very much appreciated. > > best regards flyingimmi > > -- > View this message in context: > http://www.nabble.com/Read-numbers-from-java-window-tp21982814p21982814.html > Sent from the OpenJDK General discussion mailing list archive at > Nabble.com. > > From flyingimmi at live.de Fri Feb 13 11:28:55 2009 From: flyingimmi at live.de (flyingimmi ----) Date: Fri, 13 Feb 2009 12:28:55 +0100 Subject: Read numbers from java window In-Reply-To: References: <21982814.post@talk.nabble.com> Message-ID: Hello, I'm sorry for being so imprecise. The program that I'm talking about is a Java application with a (swing / awt )GUI . I uploaded a screen shot: http://img10.imageshack.us/img10/5293/screenshotyq1.jpg sadly I have very little experience with swing/awt I use Qt-jambi for GUI development. Thanks Date: Fri, 13 Feb 2009 21:50:23 +1100 Subject: Re: Read numbers from java window From: allenfans at gmail.com To: flyingimmi at live.de CC: discuss at openjdk.java.net What is a java window ? Thanks On Fri, Feb 13, 2009 at 9:20 PM, Flyingimmi wrote: Hello all, I'm trying to read continuously updated numbers from a java window. ( I don't have the source code for the program) I was already able to do this using a custom OCR algorithm but this is a bit slow and too error-prone. Second I tried to find the memory address where the most recent value was stored and simply checked the same memory address over and over again. This work as well to some extend , after a changing period of time the new values where stored a different location and I was not able to get access to the updated values anymore. I can only suspect was happened but I guess some kind of memory allocation. ( I was using the Sun Java Runtime on Ubuntu 8.10 ) Since all my ideas failed so far, I'm curious if there is a chance to read number ( or characters ) from a java window if I use OpenJDK. Any hint suggesting where I can find information for this task a very much appreciated. best regards flyingimmi -- View this message in context: http://www.nabble.com/Read-numbers-from-java-window-tp21982814p21982814.html Sent from the OpenJDK General discussion mailing list archive at Nabble.com. _________________________________________________________________ http://redirect.gimas.net/?n=M0902xSearchVideo Videosuche - Ganz einfach mit der Live Search From roman.kennke at aicas.com Fri Feb 13 12:58:52 2009 From: roman.kennke at aicas.com (Roman Kennke) Date: Fri, 13 Feb 2009 13:58:52 +0100 Subject: OpenJDK Bugzilla server rollout In-Reply-To: <49934B6D.4050702@sun.com> References: <498D183D.8040104@sun.com> <1234340475.2340.13.camel@fedora.wildebeest.org> <17c6771e0902110946q5cc6a0b4g9b9a53482efc5c4e@mail.gmail.com> <49932B9F.10908@7gen.com> <17c6771e0902111209r468d81fbue02e78bed8380b56@mail.gmail.com> <49934B6D.4050702@sun.com> Message-ID: <49956E8C.5020908@aicas.com> Hi Dalibor, >> Ok I only just noticed this and I don't know how binding they are but: >> >> http://mail.openjdk.java.net/mailman/listinfo > Of course, that also invites a whole other class of linguistic > (lawyerese vs. regular English) and 'IANAL, but ...' problems, but those > kinds of misunderstandings are easier to fix then 'common sense' ones, > as my favorite xkcd comic at http://xkcd.com/386/ nicely explains. Thanks! You are a genius! ;-) /Roman -- Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org aicas Allerton Interworks Computer Automated Systems GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-48 USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe Gesch?ftsf?hrer: Dr. James J. Hunt From Dalibor.Topic at Sun.COM Fri Feb 13 14:14:00 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 13 Feb 2009 15:14:00 +0100 Subject: Some slides from the Free Java Meeting at Fosdem In-Reply-To: <1234515591.2290.25.camel@fedora.wildebeest.org> References: <1226948033.3264.68.camel@dijkstra.wildebeest.org> <1234515591.2290.25.camel@fedora.wildebeest.org> Message-ID: <49958028.4010109@sun.com> Mark Wielaard wrote: > Dalibor linked them all from the wiki and when there are more > presentations available we will add them (if you gave a presentation and > also want to link to your slides please do add them or ping one of us to > upload them for you): http://wiki.debian.org/Java/DevJam/2009/Fosdem > In other words: If you gave a talk at the Java Libre dev room, haven't put up your slides there yet, because you don't want really to fiddle with uploading attachments to the wiki (what's my pass again?, how does linking attachments work? etc.), just send your slides to me in a private reply to this post, and I'll take care of the upload & linking it from the main wiki page above asap. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From martinrb at google.com Fri Feb 13 17:56:16 2009 From: martinrb at google.com (Martin Buchholz) Date: Fri, 13 Feb 2009 09:56:16 -0800 Subject: JDK 7 build 47 is available at the openjdk.java.net website In-Reply-To: <49951113.6060205@sun.com> References: <49951113.6060205@sun.com> Message-ID: <1ccfd1c10902130956i2b821e1dia10191839b3cfa17@mail.gmail.com> Hi Xiomara, The tag jdk7-b47 doesn't exist in the MASTER forest yet. In the past, I've noticed that the tag took a few hours after your announcement to come into existence, but not generally overnight. I suggest changing the release engineering process at Sun to make the tag for the release in the MASTER a prerequisite for the promoted build release announcement, to make things easier for user scripts that build binaries at a comparable code base to the binary releases for Sun's proprietary jdk7 releases. (I hope you don't mind me continuing to send you bug reports...) Martin On Thu, Feb 12, 2009 at 22:20, Xiomara Jayasena wrote: > > > The OpenJDK source is available at: > http://hg.openjdk.java.net/jdk7/jdk7 > http://hg.openjdk.java.net/jdk7/jdk7/rev/d7744e86dedc > > The OpenJDK source binary plugs for the promoted JDK 7 build 47 are > available under the openjdk http://openjdk.java.net website under Source > Code (direct link to bundles: http://download.java.net/openjdk/jdk7) > > Summary of changes: > http://download.java.net/jdk7/changes/jdk7-b47.html > > > -Xiomara > > From neal at gafter.com Fri Feb 13 18:37:05 2009 From: neal at gafter.com (Neal Gafter) Date: Fri, 13 Feb 2009 10:37:05 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: <493F2033.70207@sun.com> References: <493D9B42.6050902@sun.com> <493F2033.70207@sun.com> Message-ID: <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> Jonathan- It's been two months since this project was approved. The announcements section on http://openjdk.java.net/ does not reflect the creation of this project, and there isn't yet any repository or mailing list. I hope there isn't a problem? Regards, Neal On Tue, Dec 9, 2008 at 5:49 PM, Jonathan Gibbons wrote: > The vote is already almost unanimous, with the following having all voted > in favor: > Alex, Maurizio, Joe, Neal, Jonathan, John and Kumar > > Therefore I am calling the result early, and am pleased to announce > the Compiler Group will sponsor this Project. > > -- Jon > > > Jonathan Gibbons wrote: > > > Question: Should the Compiler Group sponsor the proposed > "Small language changes for JDK 7" Project [1]? > > Please cast your vote by replying, publicly, to this message with > either > > Vote: yes > > or > > Vote: no > > as the first line of the message body. > > You may, at your option, indicate the reason for your decision on > subsequent lines. > > Votes must be cast in the open; votes sent as private replies will > not be counted. > > The sponsorship decision will be made by a simple majority vote of > the Group's Members. Votes are due by midnight UTC next Monday, > 15 December. As an optimization, if an absolute majority of the > Group's Members votes one way or the other prior to that time then > the decision may be rendered earlier. > > Only Members of the Compiler' Group are eligible to vote on this > decision. The current Members are: > Alex Buckley > Maurizio Cimadamore > Iris Clark > Joe Darcy > Neal Gafter > Jonathan Gibbons > John Rose > Kumar Srinivasan > > Once a decision has been made the votes will be summarized and > reported to this list and also to discuss at openjdk.java.net. > > -- Jon > > [1] > http://mail.openjdk.java.net/pipermail/announce/2008-December/000065.html > > > From Jonathan.Gibbons at Sun.COM Fri Feb 13 18:45:27 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 13 Feb 2009 10:45:27 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> References: <493D9B42.6050902@sun.com> <493F2033.70207@sun.com> <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> Message-ID: <4995BFC7.8070403@sun.com> Neal, Thank you for your concern. As far as I know, there is no issue here other than the sometimes glacial pace at which things happen. I would look to Joe's blog for the latest news on this project, and I presume that he will have the repositories created when there is something to put in them. -- Jon Neal Gafter wrote: > Jonathan- > > It's been two months since this project was approved. The > announcements section on http://openjdk.java.net/ does not reflect the > creation of this project, and there isn't yet any repository or > mailing list. I hope there isn't a problem? > > Regards, > Neal > > On Tue, Dec 9, 2008 at 5:49 PM, Jonathan Gibbons > > wrote: > > The vote is already almost unanimous, with the following having > all voted > in favor: > Alex, Maurizio, Joe, Neal, Jonathan, John and Kumar > > Therefore I am calling the result early, and am pleased to announce > the Compiler Group will sponsor this Project. > > -- Jon > > > Jonathan Gibbons wrote: >> >> Question: Should the Compiler Group sponsor the proposed >> "Small language changes for JDK 7" Project [1]? >> >> Please cast your vote by replying, publicly, to this message with >> either >> >> Vote: yes >> >> or >> >> Vote: no >> >> as the first line of the message body. >> >> You may, at your option, indicate the reason for your decision on >> subsequent lines. >> >> Votes must be cast in the open; votes sent as private replies will >> not be counted. >> >> The sponsorship decision will be made by a simple majority vote of >> the Group's Members. Votes are due by midnight UTC next Monday, >> 15 December. As an optimization, if an absolute majority of the >> Group's Members votes one way or the other prior to that time then >> the decision may be rendered earlier. >> >> Only Members of the Compiler' Group are eligible to vote on this >> decision. The current Members are: >> >> Alex Buckley >> Maurizio Cimadamore >> Iris Clark >> Joe Darcy >> Neal Gafter >> Jonathan Gibbons >> John Rose >> Kumar Srinivasan >> >> Once a decision has been made the votes will be summarized and >> reported to this list and also to discuss at openjdk.java.net >> . >> >> -- Jon >> >> [1] >> http://mail.openjdk.java.net/pipermail/announce/2008-December/000065.html > > > From neal at gafter.com Fri Feb 13 19:24:55 2009 From: neal at gafter.com (Neal Gafter) Date: Fri, 13 Feb 2009 11:24:55 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: <4995BFC7.8070403@sun.com> References: <493D9B42.6050902@sun.com> <493F2033.70207@sun.com> <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> <4995BFC7.8070403@sun.com> Message-ID: <15e8b9d20902131124h16ffa4feie50bd810877f2632@mail.gmail.com> Thanks. I'm more interested in the mailing list than the repository, as that is where proposals are supposed to be submitted. On Fri, Feb 13, 2009 at 10:45 AM, Jonathan Gibbons wrote: > Neal, > > Thank you for your concern. As far as I know, there is no issue here > other than the sometimes glacial pace at which things happen. I would look > to Joe's blog for the latest news on this project, and I presume that he > will have the repositories created when there is something to put in them. > From Jonathan.Gibbons at Sun.COM Fri Feb 13 19:28:10 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 13 Feb 2009 11:28:10 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: <15e8b9d20902131124h16ffa4feie50bd810877f2632@mail.gmail.com> References: <493D9B42.6050902@sun.com> <493F2033.70207@sun.com> <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> <4995BFC7.8070403@sun.com> <15e8b9d20902131124h16ffa4feie50bd810877f2632@mail.gmail.com> Message-ID: <4995C9CA.40303@sun.com> Neal, I'll make sure Mark sees your comment and gets things set up for this. -- Jon Neal Gafter wrote: > Thanks. I'm more interested in the mailing list than the repository, > as that is where proposals are supposed to be submitted. > > On Fri, Feb 13, 2009 at 10:45 AM, Jonathan Gibbons > > wrote: > > Neal, > > Thank you for your concern. As far as I know, there is no issue > here other than the sometimes glacial pace at which things happen. > I would look to Joe's blog for the latest news on this project, > and I presume that he will have the repositories created when > there is something to put in them. > From Joe.Darcy at Sun.COM Fri Feb 13 19:33:09 2009 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Fri, 13 Feb 2009 11:33:09 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: <4995BFC7.8070403@sun.com> References: <493D9B42.6050902@sun.com> <493F2033.70207@sun.com> <15e8b9d20902131037la60d672te3460607ee691724@mail.gmail.com> <4995BFC7.8070403@sun.com> Message-ID: <4995CAF5.6060906@sun.com> Hello. No problem; the project mailing list, etc. will be created next week; going to FOSDEM was fun but very tiring! -Joe Jonathan Gibbons wrote: > Neal, > > Thank you for your concern. As far as I know, there is no issue here > other than the sometimes glacial pace at which things happen. I would > look to Joe's blog for the latest news on this project, and I presume > that he will have the repositories created when there is something to > put in them. > > -- Jon > > Neal Gafter wrote: >> Jonathan- >> >> It's been two months since this project was approved. The >> announcements section on http://openjdk.java.net/ does not reflect >> the creation of this project, and there isn't yet any repository or >> mailing list. I hope there isn't a problem? >> >> Regards, >> Neal >> >> On Tue, Dec 9, 2008 at 5:49 PM, Jonathan Gibbons >> > wrote: >> >> The vote is already almost unanimous, with the following having >> all voted >> in favor: >> Alex, Maurizio, Joe, Neal, Jonathan, John and Kumar >> >> Therefore I am calling the result early, and am pleased to announce >> the Compiler Group will sponsor this Project. >> >> -- Jon >> >> >> Jonathan Gibbons wrote: >>> >>> Question: Should the Compiler Group sponsor the proposed >>> "Small language changes for JDK 7" Project [1]? >>> >>> Please cast your vote by replying, publicly, to this message with >>> either >>> >>> Vote: yes >>> >>> or >>> >>> Vote: no >>> >>> as the first line of the message body. >>> >>> You may, at your option, indicate the reason for your decision on >>> subsequent lines. >>> >>> Votes must be cast in the open; votes sent as private replies will >>> not be counted. >>> >>> The sponsorship decision will be made by a simple majority vote of >>> the Group's Members. Votes are due by midnight UTC next Monday, >>> 15 December. As an optimization, if an absolute majority of the >>> Group's Members votes one way or the other prior to that time then >>> the decision may be rendered earlier. >>> >>> Only Members of the Compiler' Group are eligible to vote on this >>> decision. The current Members are: >>> >>> Alex Buckley >>> Maurizio Cimadamore >>> Iris Clark >>> Joe Darcy >>> Neal Gafter >>> Jonathan Gibbons >>> John Rose >>> Kumar Srinivasan >>> >>> Once a decision has been made the votes will be summarized and >>> reported to this list and also to discuss at openjdk.java.net >>> . >>> >>> -- Jon >>> >>> [1] >>> >>> http://mail.openjdk.java.net/pipermail/announce/2008-December/000065.html >>> >> >> >> > From Xiomara.Jayasena at Sun.COM Fri Feb 13 20:06:54 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara.Jayasena at Sun.COM) Date: Fri, 13 Feb 2009 12:06:54 -0800 Subject: JDK 7 build 47 is available at the openjdk.java.net website In-Reply-To: <1ccfd1c10902130956i2b821e1dia10191839b3cfa17@mail.gmail.com> References: <49951113.6060205@sun.com> <1ccfd1c10902130956i2b821e1dia10191839b3cfa17@mail.gmail.com> Message-ID: <4995D2DE.5010304@Sun.COM> Hi Martin, On 02/13/09 09:56, Martin Buchholz wrote: > Hi Xiomara, > > The tag jdk7-b47 doesn't exist in the MASTER forest yet. > In the past, I've noticed that the tag took a few hours after your announcement > to come into existence, but not generally overnight. > > I suggest changing the release engineering process at Sun to > make the tag for the release in the MASTER a prerequisite > for the promoted build release announcement, to make things easier > for user scripts that build binaries at a comparable code base to the > binary releases for Sun's proprietary jdk7 releases. > Yes, that is the reason that tags are not use in the announcements, revs/changesets are always there and available at anytime. > (I hope you don't mind me continuing to send you bug reports...) > Please keep them coming, that is how we'll learn and hopefully get better :-) When possible we'll change processes/procedures based on feedback. Thanks again, -Xiomara > Martin > > On Thu, Feb 12, 2009 at 22:20, Xiomara Jayasena > wrote: > >> The OpenJDK source is available at: >> http://hg.openjdk.java.net/jdk7/jdk7 >> http://hg.openjdk.java.net/jdk7/jdk7/rev/d7744e86dedc >> >> The OpenJDK source binary plugs for the promoted JDK 7 build 47 are >> available under the openjdk http://openjdk.java.net website under Source >> Code (direct link to bundles: http://download.java.net/openjdk/jdk7) >> >> Summary of changes: >> http://download.java.net/jdk7/changes/jdk7-b47.html >> >> >> -Xiomara >> >> >> From flyingimmi at live.de Fri Feb 13 22:31:27 2009 From: flyingimmi at live.de (flyingimmi ----) Date: Fri, 13 Feb 2009 23:31:27 +0100 Subject: Read numbers from java window In-Reply-To: <4995C131.1030702@sun.com> References: <21982814.post@talk.nabble.com> <4995C131.1030702@sun.com> Message-ID: Hey John, thanks for the very interesting input! As far as I understand by now it's only possible to access components (for example a label) if they implement the Accessible interface. This seems not to be case for the label I'm trying to read values from, but I will continue to dig deeper into this topic. Flyingimmi Date: Fri, 13 Feb 2009 10:51:29 -0800 From: john.pampuch at sun.com Subject: Re: Read numbers from java window To: flyingimmi at live.de CC: allenfans at gmail.com; discuss at openjdk.java.net I'm not an expert on this topic, but it seems like you could use the accessibility APIs to get the data you want. There are probably even better ways too. http://java.sun.com/javase/6/docs/api/javax/accessibility/package-summary.html -John _________________________________________________________________ http://redirect.gimas.net/?n=M0902xWLM2009 Neu: Messenger 2009! Hier kostenlos downloaden! From Tim.Bell at Sun.COM Tue Feb 17 16:49:31 2009 From: Tim.Bell at Sun.COM (Tim Bell) Date: Tue, 17 Feb 2009 08:49:31 -0800 Subject: OpenJDK Community Code Review server rollout In-Reply-To: <49999E90.507@sun.com> References: <498A851A.5060605@sun.com> <49999E90.507@sun.com> Message-ID: <499AEA9B.2090506@sun.com> Ivan: > I'd like to use cr.openjdk.java.net for a public review. > How to set/reset password to that site? cr.openjdk.java.net is using the same ssh public key that you registered when you became a contributor to hg.openjdk.java.net. > If it is the same is the as for openjdk.java.net I probably do not have > the right permissions. If you are not running ssh-agent, you should be prompted for your public key passphrase. For example: % sftp cr.openjdk.java.net Connecting to cr.openjdk.java.net... Enter passphrase for key '/x/tbell/.ssh/id_dsa': If you are getting a 'password' prompt, then something is wrong with the public key negotiations and you need to fix that first. The extra-verbose output of 'sftp -vvv cr.openjdk.java.net' may help you see where the public key handshaking breaks down. Hope this helps- Tim From Edward.Kuns at Aspect.com Tue Feb 17 18:34:26 2009 From: Edward.Kuns at Aspect.com (Kuns, Edward) Date: Tue, 17 Feb 2009 13:34:26 -0500 Subject: Where does one fix a Java Web Start bug in openjdk 6? Message-ID: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> Looking in the openjdk 6 source tree, I don't see the javax.jnlp source tree anywhere. In Java 6u2, this code is at: deploy/src/javaws/share/classes/javax/jnlp but in the openjdk (openjdk-6-src-b14-25_nov_2008.tar.gz) there is no directory named "jnlp". Is Web Start included in the openjdk? I see it in openjdk 7 (jdk-7-ea-src-b47-jrl-12_feb_2009.jar), but openjdk 6 is missing the entire "deploy" directory tree. If I submit a fairly trivial fix to openjdk7 in the Web Start area, is this fix likely to get brought back to openjdk6 and back to JDK 6? (Comparing JDK6u2 and jdk-7-b47, this file is little changed.) Also, looking at the list of mailing lists at http://mail.openjdk.java.net/mailman/listinfo, I don't see a page that seems to apply to Web Start or Applets. What list is the most appropriate place to discuss Web Start issues? Thanks, Eddie -- Edward Kuns Technical Staff Member Aspect 630 227 8070? office 630 227 8165? fax edward.kuns at aspect.com www.aspect.com Unified Communications Software and Consulting Services From Dalibor.Topic at Sun.COM Tue Feb 17 18:44:48 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Tue, 17 Feb 2009 19:44:48 +0100 Subject: Where does one fix a Java Web Start bug in openjdk 6? In-Reply-To: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> References: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> Message-ID: <499B05A0.2080203@sun.com> Kuns, Edward wrote: > Looking in the openjdk 6 source tree, I don't see the javax.jnlp source tree anywhere. Hi Edward, the new plugin code and the web start haven't been released as part of OpenJDK yet. They should become part of OpenJDK in a few months : http://blogs.sun.com/darcy/date/20090116 but at this point, if you want to send in a patch the plugin & webstart implementation in Sun's JDK, you should do it through the corresponding projects on java.net. If you are using a Linux distributions, they typically distribute OpenJDK 6 with an independent plugin and web start implementation, coming from the IcedTea project - so if you want to submit a patch to that code base, the best way to go about it is to send it to the distro-pkg-dev mailing list. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From mr at sun.com Tue Feb 17 20:55:41 2009 From: mr at sun.com (Mark Reinhold) Date: Tue, 17 Feb 2009 12:55:41 -0800 Subject: CFV: Project sponsorship: Small language changes In-Reply-To: joe.darcy@sun.com; Fri, 13 Feb 2009 11:33:09 PST; <4995CAF5.6060906@sun.com> Message-ID: <20090217205541.6D6C02917EF@eggemoggin.niobe.net> > Date: Fri, 13 Feb 2009 11:33:09 -0800 > From: joe.darcy at sun.com > No problem; the project mailing list, etc. will be created next week; > going to FOSDEM was fun but very tiring! Just for the record: The delay in creating this new Project has nothing to do with glacial processes, bureaucratic or otherwise. Joe specifically requested this delay. - Mark From mr at sun.com Thu Feb 19 04:49:23 2009 From: mr at sun.com (Mark Reinhold) Date: Wed, 18 Feb 2009 20:49:23 -0800 Subject: Request for comments: New Bugzilla-based contribution process Message-ID: <20090219044923.DAB37CFD3@callebaut.niobe.net> Now that we have Bugzilla up and running [1] (thanks, Brad!), it's time to revise the existing e-mail-based patch-contribution process [2]. I've posted a first draft [3] on our shiny new code-review server (thanks, Tim!). Comments welcome. - Mark [1] http://mail.openjdk.java.net/pipermail/announce/2009-February/000069.html [2] http://openjdk.java.net/contribute/ [3] http://cr.openjdk.java.net/~mr/new-contrib.html From neal at gafter.com Thu Feb 19 05:49:17 2009 From: neal at gafter.com (Neal Gafter) Date: Wed, 18 Feb 2009 21:49:17 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <20090219044923.DAB37CFD3@callebaut.niobe.net> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: <15e8b9d20902182149j5db12d68ucc3992bd2bbbcb25@mail.gmail.com> Mark- Is there any mechanism for contributors or committers to "claim" a bug - that is, notify others that they're working on it - other than email? Given the contribution process you outlined, the main mechanism seems to be creating a bugzilla bug, but is there any way to see that the bugzilla bug has been created from the bugs.sun.com page? -Neal On Wed, Feb 18, 2009 at 8:49 PM, Mark Reinhold wrote: > Now that we have Bugzilla up and running [1] (thanks, Brad!), it's time > to revise the existing e-mail-based patch-contribution process [2]. > > I've posted a first draft [3] on our shiny new code-review server > (thanks, Tim!). Comments welcome. > > - Mark > > > [1] > http://mail.openjdk.java.net/pipermail/announce/2009-February/000069.html > [2] http://openjdk.java.net/contribute/ > [3] http://cr.openjdk.java.net/~mr/new-contrib.html > From mr at sun.com Thu Feb 19 06:16:00 2009 From: mr at sun.com (Mark Reinhold) Date: Wed, 18 Feb 2009 22:16:00 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: neal@gafter.com; Wed, 18 Feb 2009 21:49:17 PST; <15e8b9d20902182149j5db12d68ucc3992bd2bbbcb25@mail.gmail.com> Message-ID: <20090219061600.C772ACFD3@callebaut.niobe.net> > Date: Wed, 18 Feb 2009 21:49:17 -0800 > From: Neal Gafter > Is there any mechanism for contributors or committers to "claim" a bug - > that is, notify others that they're working on it - other than email? Given > the contribution process you outlined, the main mechanism seems to be > creating a bugzilla bug, Right. As stated this process doesn't really have a "claim" mechanism, since presumably you'd like to claim a bug before doing a lot of work on it. Perhaps the process should suggest that you create a Bugzilla entry first in order to stake a claim, and then attach the patch and request a sponsor once your work is complete. If two or more developers want to argue about the best way to fix a bug then they can do that in Bugzilla, where a record will be kept for all to see. > but is there any way to see that the bugzilla bug > has been created from the bugs.sun.com page? That'd be ideal, but unfortunately it takes an absurdly long time to get even the most trivial types of changes made to bugs.sun.com. To see if someone is working on a particular Sun bug I'm afraid the best approach will be just to search all bugs.openjdk.java.net bugs for comments containing the Sun bug's seven-digit id. - Mark From mr at sun.com Thu Feb 19 22:16:35 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 19 Feb 2009 14:16:35 -0800 Subject: Last call: OpenJDK Trademark Notice v1.2 Message-ID: <20090219221636.01C0928CFE3@eggemoggin.niobe.net> I proposed version 1.2 of the OpenJDK Trademark Notice last March [1], but due to other priorities never got around to making it the official version. The draft of v1.2 is attached below. To recap, the differences from v1.1 [2] are: - The term "Owner" has been changed to "Trademark Owner", just to make it absolutely clear that Sun is not, in this Notice, claiming ownership of anything other than the "OpenJDK" trademark; - The list of URLs from which the original code may be downloaded has been corrected and clarified, and also generalized to allow successor locations to be designated in the future; - A clause has been added to allow porting efforts to use the trademark; and - A clause has been added to allow downstream repackagers to use the HotSpot code from a different source tree if necessary, e.g. in order to use the C++ interpreter that's available in the jdk7 tree but not in the jdk6 tree. I'll finalize this new version, publish it, and push it into the JDK 6 and 7 source trees on or after 1 March unless someone raises substantive objections in the meantime. - Mark [1] http://mail.openjdk.java.net/pipermail/discuss/2008-March/001115.html [2] http://openjdk.java.net/legal/openjdk-trademark-notice.html -------------- next part -------------- OpenJDK Trademark Notice DRAFT Version 1.2, 2008/3/20 OpenJDK (the "Name") is a trademark of Sun Microsystems, Inc. (the "Trademark Owner"). Trademark Owner publishes source code (the "Original Software") at several World Wide Web locations (each a "Website"). These locations include: http://download.java.net/openjdk/jdk6 http://download.java.net/openjdk/jdk7 http://hg.openjdk.java.net/jdk6/jdk6 http://hg.openjdk.java.net/jdk7/jdk7 as well as any successor locations designated by Trademark Owner in future revisions of this Notice. Each Website provides Original Software in two parts: A Java virtual machine (the "Virtual Machine") and an API library and tools (the "Library and Tools"). Trademark Owner permits any person obtaining a copy of this software (the "Software") that is based on Original Software to use the Name in the package names and version strings of the Software subject to the following conditions: (1) The Software is a substantially complete implementation of the OpenJDK development-kit or runtime-environment source code retrieved from a single Website, and the vast majority of the Software code is identical to that upstream Original Software, except that: (a) Changes required to port Original Software to new operating systems or hardware architectures are permitted, so long as that work takes place in the context of an approved Project hosted in the OpenJDK Community; and (b) A Virtual Machine from one Website may be combined with the Library and Tools of another Website, so long as the vast majority of the code in each is identical to the corresponding upstream Virtual Machine or Library and Tools component. (2) No permission is hereby granted to use the Name in any other manner, unless such use constitutes "fair use", for example "based on the OpenJDK source code" or "Ubuntu's packaging of the OpenJDK 6 code". (3) Trademark Owner makes no warranties of any kind respecting the Name and all representations and warranties, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement are hereby disclaimed. (4) Finally, this notice and the following legend are included in all copies of the Software or portions of it: OpenJDK is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. Trademark Owner intends to revise this Notice as necessary in order to meet the needs of the OpenJDK Community. Please send questions or comments about this Notice to Sun Microsystems at openjdk-tm(at)sun.com. Revisions to this notice will be announced on the public mailing list announce at openjdk.java.net, to which you may subscribe by visiting http://mail.openjdk.java.net. From Bradford.Wetmore at Sun.COM Thu Feb 19 23:05:46 2009 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Thu, 19 Feb 2009 17:05:46 -0600 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <20090219044923.DAB37CFD3@callebaut.niobe.net> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: <499DE5CA.10905@sun.com> Comments on the new page first, then a response on the Mark/Neal exchange: Mark Reinhold wrote: > Now that we have Bugzilla up and running [1] (thanks, Brad!), it's time > to revise the existing e-mail-based patch-contribution process [2]. > > I've posted a first draft [3] on our shiny new code-review server > (thanks, Tim!). Comments welcome. Section 1. In the second para, there should be a link to the mail.o.j.n page and/or the group pages so that people know where to go to find other people working in the same areas. Also, add something like the following at the end of this section: Some groups have already generated lists of "starter bugs" that might contain useful ideas to get started. Section 3. People are still signing up for accounts and registering to watch specific product categories and components, so there should be a bit in here about "Announce your changes to the appropriate group's mailing list and request a sponsor" so that it doesn't get missed. I'd suggest putting it at the end of this section. Section 5. but rather to accept only high-quality contributions. I would suggest adding an extra sentence here to remind folks that their code could be used by millions of users, so it simply has to work. It's an awesome, but fulfilling responsibility. > Mark wrote: >> Neal wrote: >> Is there any mechanism for contributors or committers to "claim" a bug - >> that is, notify others that they're working on it - other than email? Given >> the contribution process you outlined, the main mechanism seems to be >> creating a bugzilla bug, > > As stated this process doesn't really have a "claim" mechanism, since > presumably you'd like to claim a bug before doing a lot of work on it. > Perhaps the process should suggest that you create a Bugzilla entry first > in order to stake a claim, and then attach the patch and request a > sponsor once your work is complete. If two or more developers want to > argue about the best way to fix a bug then they can do that in Bugzilla, > where a record will be kept for all to see. Just a reminder, the majority of bugs will eventually be handled directly in Bugzilla, but for now we're just using Bugzilla for accepting contributions for bugs that already have bugids in Bugtraq/Bugster (Sun's internal bug tracking system). So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of Bugzilla? If I understood this proposal right, say we have: 1) Internal user has previously filed Bugtraq id 6000000. 2) External user(s) wants to fix it, so they stake their claim in Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or description field. 3) Several users propose fixes. Finally one is accepted as "The Fix" and is attached to the Bugzilla bug id. 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes the bugzilla bug as "SUNBUG", updates the Whiteboard with "sunbug=6000000". Does that correspond to what you're thinking? Thanks, Brad From Weijun.Wang at Sun.COM Fri Feb 20 03:41:58 2009 From: Weijun.Wang at Sun.COM (Max (Weijun) Wang) Date: Fri, 20 Feb 2009 11:41:58 +0800 Subject: OT: A mailman question: how can I reply to a thread that's created before I join the alias? Message-ID: <8671F4C5-094B-4736-A9A3-C458698DE222@Sun.COM> Hi All While browsing the mail archive of an alias I'm not a member of, I find a quite interesting thread. However, even if I join the alias immediately, I cannot receive the thread. Is there any chance I can reply to that thread now? Or, I have to wait for someone else to first reply to it? Thanks Max From mr at sun.com Fri Feb 20 05:43:25 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 19 Feb 2009 21:43:25 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: bradford.wetmore@sun.com; Thu, 19 Feb 2009 17:05:46 CST; <499DE5CA.10905@sun.com> Message-ID: <20090220054325.D2C05CFD3@callebaut.niobe.net> > Date: Thu, 19 Feb 2009 17:05:46 -0600 > From: bradford.wetmore at sun.com > Comments on the new page first, then a response on the Mark/Neal exchange: Thanks for the detailed comments. > Section 1. > > In the second para, there should be a link to the mail.o.j.n page and/or > the group pages so that people know where to go to find other people > working in the same areas. Good idea. Done. > Also, add something like the following at the end of this section: > > Some groups have already generated lists of "starter bugs" that > might contain useful ideas to get started. Hmm; since this hasn't been done uniformly, and likely won't be soon, I'm a bit reluctant to advertise it. > Section 3. > > People are still signing up for accounts and registering to watch > specific product categories and components, so there should be a bit in > here about "Announce your changes to the appropriate group's mailing > list and request a sponsor" so that it doesn't get missed. I'd suggest > putting it at the end of this section. I'm not sure this is such a good idea. The whole point of using Bugzilla for contributions is to avoid relying upon people reading e-mail to see that a contribution has come in. I'd rather not encourage contributors to send such e-mails, which in the worst case could be perceived by potential sponsors as little more than spam. We already intend to review the incoming sponsorship requests on a regular basis and ping likely sponsors; that should be sufficient. > Section 5. > > but rather to accept only high-quality contributions. > > I would suggest adding an extra sentence here to remind folks that their > code could be used by millions of users, so it simply has to work. It's > an awesome, but fulfilling responsibility. Good point. Done. >> Mark wrote: >>> Neal wrote: >>> Is there any mechanism for contributors or committers to "claim" a bug - >>> that is, notify others that they're working on it - other than >>> email? Given >>> the contribution process you outlined, the main mechanism seems to be >>> creating a bugzilla bug, >> >> As stated this process doesn't really have a "claim" mechanism, since >> presumably you'd like to claim a bug before doing a lot of work on it. >> Perhaps the process should suggest that you create a Bugzilla entry first >> in order to stake a claim, and then attach the patch and request a >> sponsor once your work is complete. If two or more developers want to >> argue about the best way to fix a bug then they can do that in Bugzilla, >> where a record will be kept for all to see. > > Just a reminder, the majority of bugs will eventually be handled > directly in Bugzilla, Right. > but for now we're just using Bugzilla for > accepting contributions for bugs that already have bugids in > Bugtraq/Bugster (Sun's internal bug tracking system). Well, not exactly. Contributors are also welcome to submit patches for bugs or RFEs that do not already have corresponding Sun bug ids. > So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of Bugzilla? > > If I understood this proposal right, say we have: > > 1) Internal user has previously filed Bugtraq id 6000000. > 2) External user(s) wants to fix it, so they stake their claim in > Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or > description field. > 3) Several users propose fixes. Finally one is accepted as "The Fix" > and is attached to the Bugzilla bug id. > 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes the > bugzilla bug as "SUNBUG", updates the Whiteboard with "sunbug=6000000". > > Does that correspond to what you're thinking? Not quite. The SUNBUG resolution value is intended for the case of a Bugzilla bug filed against a component whose bugs are only being tracked in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is more generally useful. I think your scenario would work better as: 1) Internal user has previously filed Bugtraq id 6000000. 2) External user(s) wants to fix it, so they stake their claim in Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the bug's whiteboard. 3) Several users propose fixes. Finally one is accepted as "The Fix" and is attached to the Bugzilla bug. 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and closes the bug as FIXDELIVERED/FIXED. This does point out the need for a corresponding "How to sponsor" page, but let's try to get the "how to contribute" page done first. I've posted a revised draft [1] incorporating the above changes. On further thought I'm not going to add a "claim your bug" step just yet, the possibility of which I mentioned last night in response to Neal's comment. Let's see how things go and to what extent collisions actually occur before we add complexity to the process. - Mark [1] http://cr.openjdk.java.net/~mr/new-contrib.html From Xiomara.Jayasena at Sun.COM Fri Feb 20 06:04:47 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Thu, 19 Feb 2009 22:04:47 -0800 Subject: JDK 7 build 48 is available at the openjdk.java.net website Message-ID: <499E47FF.20905@sun.com> The OpenJDK source is available at: http://hg.openjdk.java.net/jdk7/jdk7 http://hg.openjdk.java.net/jdk7/jdk7/rev/4ae9f4bfdb98 The OpenJDK source binary plugs for the promoted JDK 7 build 48 are available under the openjdk http://openjdk.java.net website under Source Code (direct link to bundles: http://download.java.net/openjdk/jdk7) Summary of changes: http://download.java.net/jdk7/changes/jdk7-b48.html -Xiomara From volker.simonis at gmail.com Fri Feb 20 11:33:29 2009 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 20 Feb 2009 12:33:29 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <20090219044923.DAB37CFD3@callebaut.niobe.net> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: Hi Mark, I'm really happy that the Bugzilla is finally up and running. There is however one point, which hasn't been addressed until now. It is already hard to find all the information which belongs to a bug or changeset. The easy way is from changeset to bug, but the other way round, from Bug to changeset is already harder, because not every bug links to the corresponding changeset. Not to mention the webrevs and the discussions about the webrevs which happened on the mailing list (see [1] for a previous discussion on this topic). Now we get just two more system, the Bugzilla bug tracker and the Community Code Review site [2]. While this is good thing in general, how can we ensure that not only the bugzilla entry links to the Sun bug via the "sunbug" entry, but also the Sun bug links back to the corresponding Bugzilla entry. And how can we ensure to have a link from the changelist and/or from the bug to the codereview? The Bugzilla instance offers the great opportunity that discussions about a webrev can take place in the open, inside Bugzilla and are preserved there together with the bug. On the other hand, this hides the discussions about webrevs from the lists. I don't know Bugzilla, but perhaps it is possible to forward all changes of bugs from a certain category(e.g. hotspot), to the corresponding mailing list? What are your opinions about how we can get a consistent view of all the information belonging to a bug? Regards, Volker [1] http://mail.openjdk.java.net/pipermail/hotspot-dev/2008-October/000756.html [2] http://cr.openjdk.java.net/ On 2/19/09, Mark Reinhold wrote: > Now that we have Bugzilla up and running [1] (thanks, Brad!), it's time > to revise the existing e-mail-based patch-contribution process [2]. > > I've posted a first draft [3] on our shiny new code-review server > (thanks, Tim!). Comments welcome. > > - Mark > > > [1] http://mail.openjdk.java.net/pipermail/announce/2009-February/000069.html > [2] http://openjdk.java.net/contribute/ > [3] http://cr.openjdk.java.net/~mr/new-contrib.html > From Dalibor.Topic at Sun.COM Fri Feb 20 13:42:18 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 20 Feb 2009 14:42:18 +0100 Subject: OT: A mailman question: how can I reply to a thread that's created before I join the alias? In-Reply-To: <8671F4C5-094B-4736-A9A3-C458698DE222@Sun.COM> References: <8671F4C5-094B-4736-A9A3-C458698DE222@Sun.COM> Message-ID: <499EB33A.6020505@sun.com> Max (Weijun) Wang wrote: > Hi All > > While browsing the mail archive of an alias I'm not a member of, I > find a quite interesting thread. However, even if I join the alias > immediately, I cannot receive the thread. Is there any chance I can > reply to that thread now? If the list is available on gmane.org, you may be able to reply from there. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From Weijun.Wang at Sun.COM Fri Feb 20 14:11:07 2009 From: Weijun.Wang at Sun.COM (Max (Weijun) Wang) Date: Fri, 20 Feb 2009 22:11:07 +0800 Subject: OT: A mailman question: how can I reply to a thread that's created before I join the alias? In-Reply-To: <499EB33A.6020505@sun.com> References: <8671F4C5-094B-4736-A9A3-C458698DE222@Sun.COM> <499EB33A.6020505@sun.com> Message-ID: Oh, this is great. I find the list there, gmane.comp.version- control.mercurial.general. Thanks Max On Feb 20, 2009, at 9:42 PM, Dalibor Topic wrote: > Max (Weijun) Wang wrote: >> Hi All >> >> While browsing the mail archive of an alias I'm not a member of, I >> find a quite interesting thread. However, even if I join the alias >> immediately, I cannot receive the thread. Is there any chance I can >> reply to that thread now? > > If the list is available on gmane.org, you may be able to reply from > there. > > cheers, > dalibor topic > > -- > ******************************************************************* > Dalibor Topic Tel: (+49 40) 23 646 738 > Java F/OSS Ambassador AIM: robiladonaim > Sun Microsystems GmbH Mobile: (+49 177) 2664 192 > Nagelsweg 55 http://openjdk.java.net > D-20097 Hamburg mailto:Dalibor.Topic at sun.com > Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten > Amtsgericht M?nchen: HRB 161028 > Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer > Vorsitzender des Aufsichtsrates: Martin H?ring > > > From Dalibor.Topic at Sun.COM Fri Feb 20 14:16:34 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 20 Feb 2009 15:16:34 +0100 Subject: OT: A mailman question: how can I reply to a thread that's created before I join the alias? In-Reply-To: References: <8671F4C5-094B-4736-A9A3-C458698DE222@Sun.COM> <499EB33A.6020505@sun.com> Message-ID: <499EBB42.90205@sun.com> Max (Weijun) Wang wrote: > Oh, this is great. Yeah, that's the typical reaction to gmane. ;) cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From Dalibor.Topic at Sun.COM Fri Feb 20 15:39:01 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 20 Feb 2009 16:39:01 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: References: <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: <499ECE95.9080608@sun.com> Volker Simonis wrote: > I don't know Bugzilla, but > perhaps it is possible to forward all changes of bugs from a certain > category(e.g. hotspot), to the corresponding mailing list? > Almost - then people usually start complaining about being overwhelmed by bug traffic about issues they don't care about. ;) What I think we should have are bug watcher mailing lists for each product in Bugzilla, that people interested in a specific area can subscribe to and get their fill of updates that way, rather then dumping them on the regular list, in between the other review traffic, discussions, etc. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From volker.simonis at gmail.com Fri Feb 20 15:50:49 2009 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 20 Feb 2009 16:50:49 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <499ECE95.9080608@sun.com> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> <499ECE95.9080608@sun.com> Message-ID: On 2/20/09, Dalibor Topic wrote: > Volker Simonis wrote: > > > I don't know Bugzilla, but > > perhaps it is possible to forward all changes of bugs from a certain > > category(e.g. hotspot), to the corresponding mailing list? > > > > > Almost - then people usually start complaining about being overwhelmed by > bug traffic about issues they > don't care about. ;) What I think we should have are bug watcher mailing > lists for each product in Bugzilla, > that people interested in a specific area can subscribe to and get their > fill of updates that way, rather then > dumping them on the regular list, in between the other review traffic, > discussions, etc. > Yes, I completely agree except the part "in between the other review traffic". My point was exactly that I want ALL the bits belonging to a bug report in ONE central place and not split over mailing lists for some sort of bugs, different bug tracking systems for another sort of bugs and webrevs in different locations for yet another bugs (at least in an ideal world this would be nice:). Volker From gnu_andrew at member.fsf.org Fri Feb 20 16:21:30 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Fri, 20 Feb 2009 16:21:30 +0000 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <499ECE95.9080608@sun.com> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> <499ECE95.9080608@sun.com> Message-ID: <17c6771e0902200821w7f08c441o15153394acd48164@mail.gmail.com> 2009/2/20 Dalibor Topic : > Volker Simonis wrote: >> >> I don't know Bugzilla, but >> perhaps it is possible to forward all changes of bugs from a certain >> category(e.g. hotspot), to the corresponding mailing list? >> > > Almost - then people usually start complaining about being overwhelmed by > bug traffic about issues they > don't care about. ;) What I think we should have are bug watcher mailing > lists for each product in Bugzilla, > that people interested in a specific area can subscribe to and get their > fill of updates that way, rather then > dumping them on the regular list, in between the other review traffic, > discussions, etc. > Can we make that a bug watcher mailing list (singular)? We already have a ridiculous number of lists, doubling that for watching bugs is going to make things even crazier. > cheers, > dalibor topic > > -- > ******************************************************************* > Dalibor Topic ? ? ? ? ? ? ? ? ? Tel: (+49 40) 23 646 738 > Java F/OSS Ambassador ? ? ? ? ? AIM: robiladonaim > Sun Microsystems GmbH ? ? ? ? ? Mobile: (+49 177) 2664 192 > Nagelsweg 55 ? ? ? ? ? ? ? ? ? ?http://openjdk.java.net > D-20097 Hamburg ? ? ? ? ? ? ? ? mailto:Dalibor.Topic at sun.com > Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten > Amtsgericht M?nchen: HRB 161028 > Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer > Vorsitzender des Aufsichtsrates: Martin H?ring > > > > Cheers, -- 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 gnu_andrew at member.fsf.org Fri Feb 20 16:24:28 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Fri, 20 Feb 2009 16:24:28 +0000 Subject: Last call: OpenJDK Trademark Notice v1.2 In-Reply-To: <20090219221636.01C0928CFE3@eggemoggin.niobe.net> References: <20090219221636.01C0928CFE3@eggemoggin.niobe.net> Message-ID: <17c6771e0902200824r3792b050n619576a0620cc930@mail.gmail.com> 2009/2/19 Mark Reinhold : > I proposed version 1.2 of the OpenJDK Trademark Notice last March [1], > but due to other priorities never got around to making it the official > version. > > The draft of v1.2 is attached below. ?To recap, the differences from > v1.1 [2] are: > > ?- The term "Owner" has been changed to "Trademark Owner", just to > ? ?make it absolutely clear that Sun is not, in this Notice, claiming > ? ?ownership of anything other than the "OpenJDK" trademark; > > ?- The list of URLs from which the original code may be downloaded > ? ?has been corrected and clarified, and also generalized to allow > ? ?successor locations to be designated in the future; > > ?- A clause has been added to allow porting efforts to use the > ? ?trademark; and > > ?- A clause has been added to allow downstream repackagers to use > ? ?the HotSpot code from a different source tree if necessary, e.g. > ? ?in order to use the C++ interpreter that's available in the jdk7 > ? ?tree but not in the jdk6 tree. > > I'll finalize this new version, publish it, and push it into the JDK 6 > and 7 source trees on or after 1 March unless someone raises substantive > objections in the meantime. > > - Mark > > > [1] http://mail.openjdk.java.net/pipermail/discuss/2008-March/001115.html > [2] http://openjdk.java.net/legal/openjdk-trademark-notice.html > > > > OpenJDK Trademark Notice > DRAFT Version 1.2, 2008/3/20 > > > OpenJDK (the "Name") is a trademark of Sun Microsystems, Inc. (the "Trademark > Owner"). > > Trademark Owner publishes source code (the "Original Software") at several > World Wide Web locations (each a "Website"). ?These locations include: > > ? ?http://download.java.net/openjdk/jdk6 > ? ?http://download.java.net/openjdk/jdk7 > ? ?http://hg.openjdk.java.net/jdk6/jdk6 > ? ?http://hg.openjdk.java.net/jdk7/jdk7 > > as well as any successor locations designated by Trademark Owner in future > revisions of this Notice. > > Each Website provides Original Software in two parts: A Java virtual machine > (the "Virtual Machine") and an API library and tools (the "Library and Tools"). > > Trademark Owner permits any person obtaining a copy of this software (the > "Software") that is based on Original Software to use the Name in the package > names and version strings of the Software subject to the following conditions: > > ?(1) The Software is a substantially complete implementation of the OpenJDK > ? ? ?development-kit or runtime-environment source code retrieved from a single > ? ? ?Website, and the vast majority of the Software code is identical to that > ? ? ?upstream Original Software, except that: > > ? ? ? ?(a) Changes required to port Original Software to new operating systems > ? ? ? ? ? ?or hardware architectures are permitted, so long as that work takes > ? ? ? ? ? ?place in the context of an approved Project hosted in the OpenJDK > ? ? ? ? ? ?Community; and > > ? ? ? ?(b) A Virtual Machine from one Website may be combined with the Library > ? ? ? ? ? ?and Tools of another Website, so long as the vast majority of the > ? ? ? ? ? ?code in each is identical to the corresponding upstream Virtual > ? ? ? ? ? ?Machine or Library and Tools component. > > ?(2) No permission is hereby granted to use the Name in any other manner, > ? ? ?unless such use constitutes "fair use", for example "based on the OpenJDK > ? ? ?source code" or "Ubuntu's packaging of the OpenJDK 6 code". > > ?(3) Trademark Owner makes no warranties of any kind respecting the Name and > ? ? ?all representations and warranties, including any implied warranty of > ? ? ?merchantability, fitness for a particular purpose or non-infringement are > ? ? ?hereby disclaimed. > > ?(4) Finally, this notice and the following legend are included in all copies > ? ? ?of the Software or portions of it: > > ? ? ? ? ?OpenJDK is a trademark or registered trademark of Sun Microsystems, > ? ? ? ? ?Inc. in the United States and other countries. > > Trademark Owner intends to revise this Notice as necessary in order to meet the > needs of the OpenJDK Community. ?Please send questions or comments about this > Notice to Sun Microsystems at openjdk-tm(at)sun.com. ?Revisions to this notice > will be announced on the public mailing list announce at openjdk.java.net, to > which you may subscribe by visiting http://mail.openjdk.java.net. > > Assumed this had already gone through ages ago :) We need the HotSpot clause to ship the IcedTea builds as 'OpenJDK', as we're using HS14... :) -- 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 Dmitri.Trembovetski at Sun.COM Fri Feb 20 18:10:39 2009 From: Dmitri.Trembovetski at Sun.COM (Dmitri Trembovetski) Date: Fri, 20 Feb 2009 10:10:39 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: References: <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: <499EF21F.2030201@Sun.COM> Volker Simonis wrote: > Hi Mark, > > I'm really happy that the Bugzilla is finally up and running. There is > however one point, which hasn't been addressed until now. It is > already hard to find all the information which belongs to a bug or > changeset. The easy way is from changeset to bug, but the other way > round, from Bug to changeset is already harder, because not every bug > links to the corresponding changeset. Not to mention the webrevs and > the discussions about the webrevs which happened on the mailing list > (see [1] for a previous discussion on this topic). > > Now we get just two more system, the Bugzilla bug tracker and the > Community Code Review site [2]. While this is good thing in general, > how can we ensure that not only the bugzilla entry links to the Sun > bug via the "sunbug" entry, but also the Sun bug links back to the > corresponding Bugzilla entry. And how can we ensure to have a link > from the changelist and/or from the bug to the codereview? The There could be a check-in hook which would update corresponding Bugzilla entry (and Sun internal bug id) with the changeset id and url. Thanks, Dmitri > Bugzilla instance offers the great opportunity that discussions about > a webrev can take place in the open, inside Bugzilla and are preserved > there together with the bug. On the other hand, this hides the > discussions about webrevs from the lists. I don't know Bugzilla, but > perhaps it is possible to forward all changes of bugs from a certain > category(e.g. hotspot), to the corresponding mailing list? > > What are your opinions about how we can get a consistent view of all > the information belonging to a bug? > > Regards, > Volker > > [1] http://mail.openjdk.java.net/pipermail/hotspot-dev/2008-October/000756.html > [2] http://cr.openjdk.java.net/ > > On 2/19/09, Mark Reinhold wrote: >> Now that we have Bugzilla up and running [1] (thanks, Brad!), it's time >> to revise the existing e-mail-based patch-contribution process [2]. >> >> I've posted a first draft [3] on our shiny new code-review server >> (thanks, Tim!). Comments welcome. >> >> - Mark >> >> >> [1] http://mail.openjdk.java.net/pipermail/announce/2009-February/000069.html >> [2] http://openjdk.java.net/contribute/ >> [3] http://cr.openjdk.java.net/~mr/new-contrib.html >> From Dalibor.Topic at Sun.COM Sat Feb 21 00:07:23 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Sat, 21 Feb 2009 01:07:23 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <17c6771e0902200821w7f08c441o15153394acd48164@mail.gmail.com> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> <499ECE95.9080608@sun.com> <17c6771e0902200821w7f08c441o15153394acd48164@mail.gmail.com> Message-ID: <499F45BB.9030209@sun.com> Andrew John Hughes wrote: > Can we make that a bug watcher mailing list (singular)? We already > have a ridiculous number of lists, doubling that for watching bugs is > going to make things even crazier. I think ideally we'd have both: a single list for people who enjoy the buzz of regular, fresh e-mail delivery without discriminating much about the subject, and watcher lists for each product in the bug tracker for people who are more interested in contributions in their own area, then in others. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From Jonathan.Gibbons at Sun.COM Sat Feb 21 00:32:02 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 20 Feb 2009 16:32:02 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <499F45BB.9030209@sun.com> References: <20090219044923.DAB37CFD3@callebaut.niobe.net> <499ECE95.9080608@sun.com> <17c6771e0902200821w7f08c441o15153394acd48164@mail.gmail.com> <499F45BB.9030209@sun.com> Message-ID: <499F4B82.9020900@sun.com> Why is it that after so many years of email, shared computing, Internet, etc, this is still such a difficult issue? Or if not difficult, then just unsolved. -- Jon Dalibor Topic wrote: > Andrew John Hughes wrote: >> Can we make that a bug watcher mailing list (singular)? We already >> have a ridiculous number of lists, doubling that for watching bugs is >> going to make things even crazier. > I think ideally we'd have both: a single list for people who enjoy the > buzz of regular, fresh e-mail > delivery without discriminating much about the subject, and watcher > lists for each product in the > bug tracker for people who are more interested in contributions in > their own area, then in others. > > cheers, > dalibor topic > From Bradford.Wetmore at Sun.COM Sat Feb 21 20:25:11 2009 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Sat, 21 Feb 2009 14:25:11 -0600 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <20090220054325.D2C05CFD3@callebaut.niobe.net> References: <20090220054325.D2C05CFD3@callebaut.niobe.net> Message-ID: <49A06327.9090800@sun.com> Mark wrote: >> Also, add something like the following at the end of this section: >> >> Some groups have already generated lists of "starter bugs" that >> might contain useful ideas to get started. > > Hmm; since this hasn't been done uniformly, and likely won't be soon, > I'm a bit reluctant to advertise it. You're probably right. Now that I think about it, the list we generated for the security group was about 2 years ago when Peabody was the primary project contribution mechanism, and OpenJDK was just about ready to go live. >> People are still signing up for accounts and registering to watch >> specific product categories and components, so there should be a bit in >> here about "Announce your changes to the appropriate group's mailing >> list and request a sponsor" so that it doesn't get missed. I'd suggest >> putting it at the end of this section. > > I'm not sure this is such a good idea. The whole point of using Bugzilla > for contributions is to avoid relying upon people reading e-mail to see > that a contribution has come in. I'd rather not encourage contributors > to send such e-mails, which in the worst case could be perceived by > potential sponsors as little more than spam. My original thought when I wrote this was that this would be a temporary thing until the number of new accounts slows to a trickle and people are using it often. But you're right, getting folks into that habit now would be hard to break later. > We already intend to > review the incoming sponsorship requests on a regular basis and ping > likely sponsors; that should be sufficient. Contributors, please remember to set your "sponsor" flag! ;) >> but for now we're just using Bugzilla for >> accepting contributions for bugs that already have bugids in >> Bugtraq/Bugster (Sun's internal bug tracking system). > > Well, not exactly. Contributors are also welcome to submit patches for > bugs or RFEs that do not already have corresponding Sun bug ids. Good to know, I hadn't grasped that subtlety. Maybe that could be called out a little more in Section 1? >> So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of Bugzilla? >> >> If I understood this proposal right, say we have: >> >> 1) Internal user has previously filed Bugtraq id 6000000. >> 2) External user(s) wants to fix it, so they stake their claim in >> Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or >> description field. >> 3) Several users propose fixes. Finally one is accepted as "The Fix" >> and is attached to the Bugzilla bug id. >> 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes the >> bugzilla bug as "SUNBUG", updates the Whiteboard with "sunbug=6000000". >> >> Does that correspond to what you're thinking? > > Not quite. The SUNBUG resolution value is intended for the case of a > Bugzilla bug filed against a component whose bugs are only being tracked > in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is more > generally useful. I think your scenario would work better as: > > 1) Internal user has previously filed Bugtraq id 6000000. > 2) External user(s) wants to fix it, so they stake their claim in > Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the > bug's whiteboard. > 3) Several users propose fixes. Finally one is accepted as "The Fix" > and is attached to the Bugzilla bug. > 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and > closes the bug as FIXDELIVERED/FIXED. Minor nit. When the fix is put into one of the gates, the fix goes to "fix available" in bugtraq. It's the gatekeepers who mark as Fix Delivered. This means the sponsor must watch for the change to hit the MASTER and then remember to move it to FIXDELIVERED, or else the gatekeepers must realize that he has to update both. Or just mark as FIXDELIVERED when it goes into one of the GATES? That'll be confusing. Until we get Bugtraq/Bugzilla linked, this does require someone duplicate the states in both the Bugzilla/Bugster bugids. That's something to address in the sponsor document. > On further thought I'm not going to add a "claim your bug" step just yet, > the possibility of which I mentioned last night in response to Neal's > comment. If people are following Section 2 ("discuss your intended change"), this shouldn't be necessary. Brad From millisami at gmail.com Mon Feb 23 15:52:45 2009 From: millisami at gmail.com (millisami) Date: Mon, 23 Feb 2009 07:52:45 -0800 (PST) Subject: What is the equivalent path? Message-ID: <22155695.post@talk.nabble.com> I got to setup the following two variables: export LD_LIBRARY_PATH=/usr/java/jdk1.6.0/jre/lib/i386/:/usr/java/jdk1.6.0/jre/lib/i386/client/:./ export JAVA_HOME=/usr/java/jdk1.6.0/ Since, the above is for the version of jdk installed via SunJDK, what could be the equivalent path for the openjdk-6-jdk package! My OpenJDK is installed at /usr/lib/jvm/java-6-openjdk I couldn't find the folder i386?? To which path should I point to?? -- View this message in context: http://www.nabble.com/What-is-the-equivalent-path--tp22155695p22155695.html Sent from the OpenJDK General discussion mailing list archive at Nabble.com. From volker.simonis at gmail.com Mon Feb 23 16:07:54 2009 From: volker.simonis at gmail.com (Volker Simonis) Date: Mon, 23 Feb 2009 17:07:54 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <49A06327.9090800@sun.com> References: <20090220054325.D2C05CFD3@callebaut.niobe.net> <49A06327.9090800@sun.com> Message-ID: Sorry for cross-posting, but I think the two threads are related and this post belongs into both of them: Just to name a current issue and demonstrate how complicated it may be to follow the development process, lets consider Bug ID: 6622432 (RFE: Performance improvements to java.math.BigDecimal): On the mailing lists, there was a Request for review: http://www.mail-archive.com/core-libs-dev at openjdk.java.net/msg01095.html http://webrev.invokedynamic.info/xiaobin.lu/6622432/ But I couldn't see a changeset for the bug. So apparently it is not in any of the OpenJDK 7 repositories (at least I couldn't find it). On the other hand, the Bug says "State, 8-Fix Available". Brad wrote "When the fix is put into one of the gates, the fix goes to "fix available" in bugtraq. It's the gatekeepers who mark as Fix Delivered." So apparently, the change went into a closed "gate". I would guess it could be the "JDK6 RE build" Mercurial repository mentioned by James Melvin in another thread (http://www.nabble.com/How-to-host-HS14-stable--%28Was%3A-RFC%3A-Change-name-of-default-HotSpot-to-%27default%27%29-tp22053363p22053363.html) because the list of fixed bugs for JDK 6u14 b01 (http://download.java.net/jdk6/6u14/promoted/b01/changes/JDK6u14.list.html) lists 6622432 as fixed. But this is in contradiction to the status of the bug which is "State, 8-Fix Available". So I assume there must be another Bug Id for the same problem, but neither could I find it in the bug database, nor is there a link from Bug 6622432 to this other bug. So keeping track of all these bugs and codelines is already quite difficult and shouldn't be even more complicated by the new model... Regards, Volker On 2/21/09, Brad Wetmore wrote: > > Mark wrote: > > > > > > > Also, add something like the following at the end of this section: > > > > > > Some groups have already generated lists of "starter bugs" that > > > might contain useful ideas to get started. > > > > > > > Hmm; since this hasn't been done uniformly, and likely won't be soon, > > I'm a bit reluctant to advertise it. > > > > You're probably right. Now that I think about it, the list we generated > for the security group was about 2 years ago when Peabody was the primary > project contribution mechanism, and OpenJDK was just about ready to go live. > > > > > > > People are still signing up for accounts and registering to watch > > > specific product categories and components, so there should be a bit in > > > here about "Announce your changes to the appropriate group's mailing > > > list and request a sponsor" so that it doesn't get missed. I'd suggest > > > putting it at the end of this section. > > > > > > > I'm not sure this is such a good idea. The whole point of using Bugzilla > > for contributions is to avoid relying upon people reading e-mail to see > > that a contribution has come in. I'd rather not encourage contributors > > to send such e-mails, which in the worst case could be perceived by > > potential sponsors as little more than spam. > > > > My original thought when I wrote this was that this would be a temporary > thing until the number of new accounts slows to a trickle and people are > using it often. But you're right, getting folks into that habit now would > be hard to break later. > > > > We already intend to > > review the incoming sponsorship requests on a regular basis and ping > > likely sponsors; that should be sufficient. > > > > Contributors, please remember to set your "sponsor" flag! ;) > > > > > > > but for now we're just using Bugzilla for > > > accepting contributions for bugs that already have bugids in > > > Bugtraq/Bugster (Sun's internal bug tracking system). > > > > > > > Well, not exactly. Contributors are also welcome to submit patches for > > bugs or RFEs that do not already have corresponding Sun bug ids. > > > > Good to know, I hadn't grasped that subtlety. Maybe that could be called > out a little more in Section 1? > > > > > > > So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of > Bugzilla? > > > > > > If I understood this proposal right, say we have: > > > > > > 1) Internal user has previously filed Bugtraq id 6000000. > > > 2) External user(s) wants to fix it, so they stake their claim in > > > Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or > > > description field. > > > 3) Several users propose fixes. Finally one is accepted as "The Fix" > > > and is attached to the Bugzilla bug id. > > > 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes the > > > bugzilla bug as "SUNBUG", updates the Whiteboard with "sunbug=6000000". > > > > > > Does that correspond to what you're thinking? > > > > > > > Not quite. The SUNBUG resolution value is intended for the case of a > > Bugzilla bug filed against a component whose bugs are only being tracked > > in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is more > > generally useful. I think your scenario would work better as: > > > > 1) Internal user has previously filed Bugtraq id 6000000. > > 2) External user(s) wants to fix it, so they stake their claim in > > Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the > > bug's whiteboard. > > 3) Several users propose fixes. Finally one is accepted as "The Fix" > > and is attached to the Bugzilla bug. > > 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and > > closes the bug as FIXDELIVERED/FIXED. > > > > Minor nit. When the fix is put into one of the gates, the fix goes to "fix > available" in bugtraq. It's the gatekeepers who mark as Fix Delivered. > This means the sponsor must watch for the change to hit the MASTER and then > remember to move it to FIXDELIVERED, or else the gatekeepers must realize > that he has to update both. Or just mark as FIXDELIVERED when it goes into > one of the GATES? That'll be confusing. > > Until we get Bugtraq/Bugzilla linked, this does require someone duplicate > the states in both the Bugzilla/Bugster bugids. That's something to address > in the sponsor document. > > > > On further thought I'm not going to add a "claim your bug" step just yet, > > the possibility of which I mentioned last night in response to Neal's > > comment. > > > > If people are following Section 2 ("discuss your intended change"), this > shouldn't be necessary. > > Brad > From gnu_andrew at member.fsf.org Mon Feb 23 16:34:54 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Mon, 23 Feb 2009 16:34:54 +0000 Subject: Where does one fix a Java Web Start bug in openjdk 6? In-Reply-To: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> References: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> Message-ID: <17c6771e0902230834w497aa794i58b54aa3a351e54c@mail.gmail.com> 2009/2/17 Kuns, Edward : ... >?I see it in openjdk 7 (jdk-7-ea-src-b47-jrl-12_feb_2009.jar), but openjdk 6 is missing the entire "deploy" directory tree. > ... No you don't. That's not OpenJDK7. The latest OpenJDK7 build drop is http://www.java.net/download/openjdk/jdk7/promoted/b48/openjdk-7-ea-src-b48-19_feb_2009.zip The zip you reference is the proprietary JDK7 under the Java Research License (hence the jrl in the filename and the use of jdk not openjdk). > -- > Edward Kuns > Technical Staff Member > Aspect > 630 227 8070? office > 630 227 8165? fax > edward.kuns at aspect.com > www.aspect.com > Unified Communications Software and Consulting Services > > Thanks, -- 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 Bradford.Wetmore at Sun.COM Mon Feb 23 16:42:55 2009 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Mon, 23 Feb 2009 10:42:55 -0600 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: References: <20090220054325.D2C05CFD3@callebaut.niobe.net> <49A06327.9090800@sun.com> Message-ID: <49A2D20F.2080006@sun.com> I feel your pain. Roger, Mark or someone more familiar with Bugtraq, perhaps you know the answer to this? So that the external folks can follow along, we have several states in Bugtraq (Sun's internal bug tracking system): Fix In Progress - developer is working on fix. Fix Available - Fix is available, isn't in product workspace yet. Fix Delivered - Fix is in product workspace. Bug 6622432 is tracked in bugster as a MR (Multiple Release Bug). The SR (Service Request) against one of the future Sun JDK6 update releases is marked as "Fix Delivered". The SR against 7 is marked "Fix In Progress". There is no SR currently for OpenJDK6. The external page: http://bugs.sun.com/view_bug.do?bug_id=6622432 does not mention which release this is against, and apparently splits the middle by reporting "Fix available". According to the Bugtraq log history, this has never been "Fixed available" in 7. So, what (and why) is bugs.sun.com actually reporting? Once we do most bug tracking on Bugzilla, hopefully this will go away. Brad Volker Simonis wrote: > Sorry for cross-posting, but I think the two threads are related and > this post belongs into both of them: > > Just to name a current issue and demonstrate how complicated it may be > to follow the development process, lets consider Bug ID: 6622432 (RFE: > Performance improvements to java.math.BigDecimal): > > On the mailing lists, there was a Request for review: > > http://www.mail-archive.com/core-libs-dev at openjdk.java.net/msg01095.html > http://webrev.invokedynamic.info/xiaobin.lu/6622432/ > > But I couldn't see a changeset for the bug. So apparently it is not in > any of the OpenJDK 7 repositories (at least I couldn't find it). > > On the other hand, the Bug says "State, 8-Fix Available". Brad wrote > "When the fix is put into one of the gates, the fix goes to "fix > available" in bugtraq. It's the gatekeepers who mark as Fix > Delivered." So apparently, the change went into a closed "gate". > > I would guess it could be the "JDK6 RE build" Mercurial repository > mentioned by James Melvin in another thread > (http://www.nabble.com/How-to-host-HS14-stable--%28Was%3A-RFC%3A-Change-name-of-default-HotSpot-to-%27default%27%29-tp22053363p22053363.html) > because the list of fixed bugs for JDK 6u14 b01 > (http://download.java.net/jdk6/6u14/promoted/b01/changes/JDK6u14.list.html) > lists 6622432 as fixed. But this is in contradiction to the status of > the bug which is "State, 8-Fix Available". > > So I assume there must be another Bug Id for the same problem, but > neither could I find it in the bug database, nor is there a link from > Bug 6622432 to this other bug. > > So keeping track of all these bugs and codelines is already quite > difficult and shouldn't be even more complicated by the new model... > > Regards, > Volker > > On 2/21/09, Brad Wetmore wrote: >> Mark wrote: >> >> >>>> Also, add something like the following at the end of this section: >>>> >>>> Some groups have already generated lists of "starter bugs" that >>>> might contain useful ideas to get started. >>>> >>> Hmm; since this hasn't been done uniformly, and likely won't be soon, >>> I'm a bit reluctant to advertise it. >>> >> You're probably right. Now that I think about it, the list we generated >> for the security group was about 2 years ago when Peabody was the primary >> project contribution mechanism, and OpenJDK was just about ready to go live. >> >> >>>> People are still signing up for accounts and registering to watch >>>> specific product categories and components, so there should be a bit in >>>> here about "Announce your changes to the appropriate group's mailing >>>> list and request a sponsor" so that it doesn't get missed. I'd suggest >>>> putting it at the end of this section. >>>> >>> I'm not sure this is such a good idea. The whole point of using Bugzilla >>> for contributions is to avoid relying upon people reading e-mail to see >>> that a contribution has come in. I'd rather not encourage contributors >>> to send such e-mails, which in the worst case could be perceived by >>> potential sponsors as little more than spam. >>> >> My original thought when I wrote this was that this would be a temporary >> thing until the number of new accounts slows to a trickle and people are >> using it often. But you're right, getting folks into that habit now would >> be hard to break later. >> >> >>> We already intend to >>> review the incoming sponsorship requests on a regular basis and ping >>> likely sponsors; that should be sufficient. >>> >> Contributors, please remember to set your "sponsor" flag! ;) >> >> >>>> but for now we're just using Bugzilla for >>>> accepting contributions for bugs that already have bugids in >>>> Bugtraq/Bugster (Sun's internal bug tracking system). >>>> >>> Well, not exactly. Contributors are also welcome to submit patches for >>> bugs or RFEs that do not already have corresponding Sun bug ids. >>> >> Good to know, I hadn't grasped that subtlety. Maybe that could be called >> out a little more in Section 1? >> >> >>>> So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of >> Bugzilla? >>>> If I understood this proposal right, say we have: >>>> >>>> 1) Internal user has previously filed Bugtraq id 6000000. >>>> 2) External user(s) wants to fix it, so they stake their claim in >>>> Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or >>>> description field. >>>> 3) Several users propose fixes. Finally one is accepted as "The Fix" >>>> and is attached to the Bugzilla bug id. >>>> 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes the >>>> bugzilla bug as "SUNBUG", updates the Whiteboard with "sunbug=6000000". >>>> >>>> Does that correspond to what you're thinking? >>>> >>> Not quite. The SUNBUG resolution value is intended for the case of a >>> Bugzilla bug filed against a component whose bugs are only being tracked >>> in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is more >>> generally useful. I think your scenario would work better as: >>> >>> 1) Internal user has previously filed Bugtraq id 6000000. >>> 2) External user(s) wants to fix it, so they stake their claim in >>> Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the >>> bug's whiteboard. >>> 3) Several users propose fixes. Finally one is accepted as "The Fix" >>> and is attached to the Bugzilla bug. >>> 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and >>> closes the bug as FIXDELIVERED/FIXED. >>> >> Minor nit. When the fix is put into one of the gates, the fix goes to "fix >> available" in bugtraq. It's the gatekeepers who mark as Fix Delivered. >> This means the sponsor must watch for the change to hit the MASTER and then >> remember to move it to FIXDELIVERED, or else the gatekeepers must realize >> that he has to update both. Or just mark as FIXDELIVERED when it goes into >> one of the GATES? That'll be confusing. >> >> Until we get Bugtraq/Bugzilla linked, this does require someone duplicate >> the states in both the Bugzilla/Bugster bugids. That's something to address >> in the sponsor document. >> >> >>> On further thought I'm not going to add a "claim your bug" step just yet, >>> the possibility of which I mentioned last night in response to Neal's >>> comment. >>> >> If people are following Section 2 ("discuss your intended change"), this >> shouldn't be necessary. >> >> Brad >> From Kelly.Ohair at Sun.COM Mon Feb 23 16:53:17 2009 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Mon, 23 Feb 2009 08:53:17 -0800 Subject: What is the equivalent path? In-Reply-To: <22155695.post@talk.nabble.com> References: <22155695.post@talk.nabble.com> Message-ID: <49A2D47D.8070708@sun.com> In general, it is considered a bad practice to set LD_LIBRARY_PATH in your environment, most tools should not depend on this variable. It can impact every process started up on a system, causing everyone to look in these directories repeatedly, for every shared library loaded, ahead of the system library locations. Granted some of the java startup scripts might set LD_LIBRARY_PATH, for the execution of that process and process tree, but many consider even a startup script that is forced to set LD_LIBRARY_PATH flawed. But at least it's set in a limited way. I myself try hard to not set either of these variables, and just rely on the 'java' in my PATH, but JAVA_HOME has a long history, and some Java tools may require it being set. Since I don't know where you got the OpenJDK6 binaries, nor what kind of OS and arch you are using, it's hard to comment on where the i386 directory is, but what I'm saying in general is that you should not need to know. -kto millisami wrote: > I got to setup the following two variables: > > export > LD_LIBRARY_PATH=/usr/java/jdk1.6.0/jre/lib/i386/:/usr/java/jdk1.6.0/jre/lib/i386/client/:./ > export JAVA_HOME=/usr/java/jdk1.6.0/ > > Since, the above is for the version of jdk installed via SunJDK, what could > be the equivalent path for the openjdk-6-jdk package! > My OpenJDK is installed at > > /usr/lib/jvm/java-6-openjdk > > I couldn't find the folder i386?? To which path should I point to?? > From Edward.Kuns at Aspect.com Mon Feb 23 16:55:37 2009 From: Edward.Kuns at Aspect.com (Kuns, Edward) Date: Mon, 23 Feb 2009 08:55:37 -0800 Subject: Where does one fix a Java Web Start bug in openjdk 6? In-Reply-To: <17c6771e0902230834w497aa794i58b54aa3a351e54c@mail.gmail.com> References: <737102E07761DE42ABDDB24B595E49918F1DA5DE15@ASP1CMS2.aspect.com> <17c6771e0902230834w497aa794i58b54aa3a351e54c@mail.gmail.com> Message-ID: <737102E07761DE42ABDDB24B595E49918F1DABC9E5@ASP1CMS2.aspect.com> From Andrew John Hughes > No you don't. That's not OpenJDK7. [snip] > The zip you reference is the proprietary JDK7 under the Java Research > License (hence the jrl in the filename and the use of jdk not openjdk). Oh! So https://jdk7.dev.java.net/ is *not* the openjdk! That was my confusion. Thanks for clearing this up. Otherwise I would have gone on being confused (and I'm probably not the only one). Eddie -- Edward Kuns Technical Staff Member Aspect 630 227 8070? office 630 227 8165? fax edward.kuns at aspect.com www.aspect.com Unified Communications Software and Consulting Services From Roger.Lewis at Sun.COM Mon Feb 23 17:08:57 2009 From: Roger.Lewis at Sun.COM (Roger Lewis) Date: Mon, 23 Feb 2009 09:08:57 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <49A2D20F.2080006@sun.com> References: <20090220054325.D2C05CFD3@callebaut.niobe.net> <49A06327.9090800@sun.com> <49A2D20F.2080006@sun.com> Message-ID: <49A2D829.6050900@sun.com> Brad, bugs.sun.com 'should' be a reflection of Butraq, off by at most 24 hours. In this case it appears that this bug has not been updated since BT was last updated. Which is why they do not accurately reflect Bugtraq. Field relationship: Release Fixed points to BT's Integrated State points to BT State, filtering is no longer being done. -Roger Brad Wetmore wrote: > > I feel your pain. > > Roger, Mark or someone more familiar with Bugtraq, perhaps you know > the answer to this? > > So that the external folks can follow along, we have several states in > Bugtraq (Sun's internal bug tracking system): > > Fix In Progress - developer is working on fix. > Fix Available - Fix is available, isn't in product workspace yet. > Fix Delivered - Fix is in product workspace. > > Bug 6622432 is tracked in bugster as a MR (Multiple Release Bug). The > SR (Service Request) against one of the future Sun JDK6 update > releases is marked as "Fix Delivered". The SR against 7 is marked > "Fix In Progress". There is no SR currently for OpenJDK6. > > The external page: > > http://bugs.sun.com/view_bug.do?bug_id=6622432 > > does not mention which release this is against, and apparently splits > the middle by reporting "Fix available". According to the Bugtraq log > history, this has never been "Fixed available" in 7. > > So, what (and why) is bugs.sun.com actually reporting? > > Once we do most bug tracking on Bugzilla, hopefully this will go away. > > Brad > > > Volker Simonis wrote: >> Sorry for cross-posting, but I think the two threads are related and >> this post belongs into both of them: >> >> Just to name a current issue and demonstrate how complicated it may be >> to follow the development process, lets consider Bug ID: 6622432 (RFE: >> Performance improvements to java.math.BigDecimal): >> >> On the mailing lists, there was a Request for review: >> >> http://www.mail-archive.com/core-libs-dev at openjdk.java.net/msg01095.html >> http://webrev.invokedynamic.info/xiaobin.lu/6622432/ >> >> But I couldn't see a changeset for the bug. So apparently it is not in >> any of the OpenJDK 7 repositories (at least I couldn't find it). >> >> On the other hand, the Bug says "State, 8-Fix Available". Brad wrote >> "When the fix is put into one of the gates, the fix goes to "fix >> available" in bugtraq. It's the gatekeepers who mark as Fix >> Delivered." So apparently, the change went into a closed "gate". >> >> I would guess it could be the "JDK6 RE build" Mercurial repository >> mentioned by James Melvin in another thread >> (http://www.nabble.com/How-to-host-HS14-stable--%28Was%3A-RFC%3A-Change-name-of-default-HotSpot-to-%27default%27%29-tp22053363p22053363.html) >> >> because the list of fixed bugs for JDK 6u14 b01 >> (http://download.java.net/jdk6/6u14/promoted/b01/changes/JDK6u14.list.html) >> >> lists 6622432 as fixed. But this is in contradiction to the status of >> the bug which is "State, 8-Fix Available". >> >> So I assume there must be another Bug Id for the same problem, but >> neither could I find it in the bug database, nor is there a link from >> Bug 6622432 to this other bug. >> >> So keeping track of all these bugs and codelines is already quite >> difficult and shouldn't be even more complicated by the new model... >> >> Regards, >> Volker >> >> On 2/21/09, Brad Wetmore wrote: >>> Mark wrote: >>> >>> >>>>> Also, add something like the following at the end of this section: >>>>> >>>>> Some groups have already generated lists of "starter bugs" that >>>>> might contain useful ideas to get started. >>>>> >>>> Hmm; since this hasn't been done uniformly, and likely won't be soon, >>>> I'm a bit reluctant to advertise it. >>>> >>> You're probably right. Now that I think about it, the list we >>> generated >>> for the security group was about 2 years ago when Peabody was the >>> primary >>> project contribution mechanism, and OpenJDK was just about ready to >>> go live. >>> >>> >>>>> People are still signing up for accounts and registering to watch >>>>> specific product categories and components, so there should be a >>>>> bit in >>>>> here about "Announce your changes to the appropriate group's mailing >>>>> list and request a sponsor" so that it doesn't get missed. I'd >>>>> suggest >>>>> putting it at the end of this section. >>>>> >>>> I'm not sure this is such a good idea. The whole point of using >>>> Bugzilla >>>> for contributions is to avoid relying upon people reading e-mail to >>>> see >>>> that a contribution has come in. I'd rather not encourage >>>> contributors >>>> to send such e-mails, which in the worst case could be perceived by >>>> potential sponsors as little more than spam. >>>> >>> My original thought when I wrote this was that this would be a >>> temporary >>> thing until the number of new accounts slows to a trickle and people >>> are >>> using it often. But you're right, getting folks into that habit now >>> would >>> be hard to break later. >>> >>> >>>> We already intend to >>>> review the incoming sponsorship requests on a regular basis and ping >>>> likely sponsors; that should be sufficient. >>>> >>> Contributors, please remember to set your "sponsor" flag! ;) >>> >>> >>>>> but for now we're just using Bugzilla for >>>>> accepting contributions for bugs that already have bugids in >>>>> Bugtraq/Bugster (Sun's internal bug tracking system). >>>>> >>>> Well, not exactly. Contributors are also welcome to submit patches >>>> for >>>> bugs or RFEs that do not already have corresponding Sun bug ids. >>>> >>> Good to know, I hadn't grasped that subtlety. Maybe that could be >>> called >>> out a little more in Section 1? >>> >>> >>>>> So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of >>> Bugzilla? >>>>> If I understood this proposal right, say we have: >>>>> >>>>> 1) Internal user has previously filed Bugtraq id 6000000. >>>>> 2) External user(s) wants to fix it, so they stake their claim in >>>>> Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or >>>>> description field. >>>>> 3) Several users propose fixes. Finally one is accepted as "The >>>>> Fix" >>>>> and is attached to the Bugzilla bug id. >>>>> 4) Sponsor accepts fix, integrates fix into JDK at 6000000, >>>>> closes the >>>>> bugzilla bug as "SUNBUG", updates the Whiteboard with >>>>> "sunbug=6000000". >>>>> >>>>> Does that correspond to what you're thinking? >>>>> >>>> Not quite. The SUNBUG resolution value is intended for the case of a >>>> Bugzilla bug filed against a component whose bugs are only being >>>> tracked >>>> in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is >>>> more >>>> generally useful. I think your scenario would work better as: >>>> >>>> 1) Internal user has previously filed Bugtraq id 6000000. >>>> 2) External user(s) wants to fix it, so they stake their claim in >>>> Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the >>>> bug's whiteboard. >>>> 3) Several users propose fixes. Finally one is accepted as "The Fix" >>>> and is attached to the Bugzilla bug. >>>> 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and >>>> closes the bug as FIXDELIVERED/FIXED. >>>> >>> Minor nit. When the fix is put into one of the gates, the fix goes >>> to "fix >>> available" in bugtraq. It's the gatekeepers who mark as Fix Delivered. >>> This means the sponsor must watch for the change to hit the MASTER >>> and then >>> remember to move it to FIXDELIVERED, or else the gatekeepers must >>> realize >>> that he has to update both. Or just mark as FIXDELIVERED when it >>> goes into >>> one of the GATES? That'll be confusing. >>> >>> Until we get Bugtraq/Bugzilla linked, this does require someone >>> duplicate >>> the states in both the Bugzilla/Bugster bugids. That's something to >>> address >>> in the sponsor document. >>> >>> >>>> On further thought I'm not going to add a "claim your bug" step >>>> just yet, >>>> the possibility of which I mentioned last night in response to Neal's >>>> comment. >>>> >>> If people are following Section 2 ("discuss your intended change"), >>> this >>> shouldn't be necessary. >>> >>> Brad >>> From Joe.Darcy at Sun.COM Mon Feb 23 18:03:51 2009 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Mon, 23 Feb 2009 10:03:51 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: References: <20090220054325.D2C05CFD3@callebaut.niobe.net> <49A06327.9090800@sun.com> Message-ID: <49A2E507.6090303@sun.com> Volker Simonis wrote: > Sorry for cross-posting, but I think the two threads are related and > this post belongs into both of them: > > Just to name a current issue and demonstrate how complicated it may be > to follow the development process, lets consider Bug ID: 6622432 (RFE: > Performance improvements to java.math.BigDecimal): > > On the mailing lists, there was a Request for review: > > http://www.mail-archive.com/core-libs-dev at openjdk.java.net/msg01095.html > http://webrev.invokedynamic.info/xiaobin.lu/6622432/ > > But I couldn't see a changeset for the bug. So apparently it is not in > any of the OpenJDK 7 repositories (at least I couldn't find it). > > On the other hand, the Bug says "State, 8-Fix Available". Brad wrote > "When the fix is put into one of the gates, the fix goes to "fix > available" in bugtraq. It's the gatekeepers who mark as Fix > Delivered." So apparently, the change went into a closed "gate". > > I would guess it could be the "JDK6 RE build" Mercurial repository > mentioned by James Melvin in another thread > (http://www.nabble.com/How-to-host-HS14-stable--%28Was%3A-RFC%3A-Change-name-of-default-HotSpot-to-%27default%27%29-tp22053363p22053363.html) > because the list of fixed bugs for JDK 6u14 b01 > (http://download.java.net/jdk6/6u14/promoted/b01/changes/JDK6u14.list.html) > lists 6622432 as fixed. But this is in contradiction to the status of > the bug which is "State, 8-Fix Available". > The HotSpot code is maintained a bit differently than the rest of the 6 update release train; the rest of the that release train is maintained in the legacy teamware SCM system. -Joe From Bradford.Wetmore at Sun.COM Mon Feb 23 18:31:39 2009 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Mon, 23 Feb 2009 12:31:39 -0600 Subject: [Fwd: Re: Request for comments: New Bugzilla-based contribution process] In-Reply-To: <49A2D96C.1090609@sun.com> References: <49A2D96C.1090609@sun.com> Message-ID: <49A2EB8B.2080305@sun.com> Roger, > bugs.sun.com 'should' be a reflection of Butraq, off by at most 24 > hours.In this case it appears that this bug has not been updated since > BT was last updated. Which is why they do not accurately reflect > Bugtraq. So how do people outside Sun figure if this status applies to the JDK7 or 6uX subCR from the bugs.sun.com page? It's just "a bug" on bugs.sun.com. bugs.sun.com says this was reported against b21, which from Bugtraq shows it's for the JDK7 version. But this has *NEVER* been state "Fix available" in JDK7, only "Fix in progress." For the 6uX version, it did progress to that state: 8-Fix Available 2009-01-21 22:00:49 GMT+00:00 xxx at sun.com 10-Fix Delivered 2009-01-30 22:46:17 GMT+00:00 yyy at sun.com But there's no way for folks to know which version the state applies to. I only know because I have access to bugster. Brad Roger Lewis wrote: > Ramsci > > Can you refresh bug 6622432. It is being looked at by a number of groups > and seems to be out of date. The data is Bugtraq (State and Integrated > fields) is out of sync. > > -Roger > > > ------------------------------------------------------------------------ > > Subject: > Re: Request for comments: New Bugzilla-based contribution process > From: > Brad Wetmore > Date: > Mon, 23 Feb 2009 10:42:55 -0600 > To: > Volker Simonis > > To: > Volker Simonis > CC: > Mark Reinhold , discuss at openjdk.java.net, Roger Lewis > > > > > I feel your pain. > > Roger, Mark or someone more familiar with Bugtraq, perhaps you know the > answer to this? > > So that the external folks can follow along, we have several states in > Bugtraq (Sun's internal bug tracking system): > > Fix In Progress - developer is working on fix. > Fix Available - Fix is available, isn't in product workspace yet. > Fix Delivered - Fix is in product workspace. > > Bug 6622432 is tracked in bugster as a MR (Multiple Release Bug). The > SR (Service Request) against one of the future Sun JDK6 update releases > is marked as "Fix Delivered". The SR against 7 is marked "Fix In > Progress". There is no SR currently for OpenJDK6. > > The external page: > > http://bugs.sun.com/view_bug.do?bug_id=6622432 > > does not mention which release this is against, and apparently splits > the middle by reporting "Fix available". According to the Bugtraq log > history, this has never been "Fixed available" in 7. > > So, what (and why) is bugs.sun.com actually reporting? > > Once we do most bug tracking on Bugzilla, hopefully this will go away. > > Brad > > > Volker Simonis wrote: >> Sorry for cross-posting, but I think the two threads are related and >> this post belongs into both of them: >> >> Just to name a current issue and demonstrate how complicated it may be >> to follow the development process, lets consider Bug ID: 6622432 (RFE: >> Performance improvements to java.math.BigDecimal): >> >> On the mailing lists, there was a Request for review: >> >> http://www.mail-archive.com/core-libs-dev at openjdk.java.net/msg01095.html >> http://webrev.invokedynamic.info/xiaobin.lu/6622432/ >> >> But I couldn't see a changeset for the bug. So apparently it is not in >> any of the OpenJDK 7 repositories (at least I couldn't find it). >> >> On the other hand, the Bug says "State, 8-Fix Available". Brad wrote >> "When the fix is put into one of the gates, the fix goes to "fix >> available" in bugtraq. It's the gatekeepers who mark as Fix >> Delivered." So apparently, the change went into a closed "gate". >> >> I would guess it could be the "JDK6 RE build" Mercurial repository >> mentioned by James Melvin in another thread >> (http://www.nabble.com/How-to-host-HS14-stable--%28Was%3A-RFC%3A-Change-name-of-default-HotSpot-to-%27default%27%29-tp22053363p22053363.html) >> >> because the list of fixed bugs for JDK 6u14 b01 >> (http://download.java.net/jdk6/6u14/promoted/b01/changes/JDK6u14.list.html) >> >> lists 6622432 as fixed. But this is in contradiction to the status of >> the bug which is "State, 8-Fix Available". >> >> So I assume there must be another Bug Id for the same problem, but >> neither could I find it in the bug database, nor is there a link from >> Bug 6622432 to this other bug. >> >> So keeping track of all these bugs and codelines is already quite >> difficult and shouldn't be even more complicated by the new model... >> >> Regards, >> Volker >> >> On 2/21/09, Brad Wetmore wrote: >>> Mark wrote: >>> >>> >>>>> Also, add something like the following at the end of this section: >>>>> >>>>> Some groups have already generated lists of "starter bugs" that >>>>> might contain useful ideas to get started. >>>>> >>>> Hmm; since this hasn't been done uniformly, and likely won't be soon, >>>> I'm a bit reluctant to advertise it. >>>> >>> You're probably right. Now that I think about it, the list we >>> generated >>> for the security group was about 2 years ago when Peabody was the >>> primary >>> project contribution mechanism, and OpenJDK was just about ready to >>> go live. >>> >>> >>>>> People are still signing up for accounts and registering to watch >>>>> specific product categories and components, so there should be a >>>>> bit in >>>>> here about "Announce your changes to the appropriate group's mailing >>>>> list and request a sponsor" so that it doesn't get missed. I'd >>>>> suggest >>>>> putting it at the end of this section. >>>>> >>>> I'm not sure this is such a good idea. The whole point of using >>>> Bugzilla >>>> for contributions is to avoid relying upon people reading e-mail to see >>>> that a contribution has come in. I'd rather not encourage contributors >>>> to send such e-mails, which in the worst case could be perceived by >>>> potential sponsors as little more than spam. >>>> >>> My original thought when I wrote this was that this would be a >>> temporary >>> thing until the number of new accounts slows to a trickle and people are >>> using it often. But you're right, getting folks into that habit now >>> would >>> be hard to break later. >>> >>> >>>> We already intend to >>>> review the incoming sponsorship requests on a regular basis and ping >>>> likely sponsors; that should be sufficient. >>>> >>> Contributors, please remember to set your "sponsor" flag! ;) >>> >>> >>>>> but for now we're just using Bugzilla for >>>>> accepting contributions for bugs that already have bugids in >>>>> Bugtraq/Bugster (Sun's internal bug tracking system). >>>>> >>>> Well, not exactly. Contributors are also welcome to submit patches for >>>> bugs or RFEs that do not already have corresponding Sun bug ids. >>>> >>> Good to know, I hadn't grasped that subtlety. Maybe that could be >>> called >>> out a little more in Section 1? >>> >>> >>>>> So how does this work with the SUNBUG (TRACKEDINBUGTRAQ) field of >>> Bugzilla? >>>>> If I understood this proposal right, say we have: >>>>> >>>>> 1) Internal user has previously filed Bugtraq id 6000000. >>>>> 2) External user(s) wants to fix it, so they stake their claim in >>>>> Bugzilla (Bugzilla id 100000), listing 6000000 in the summary or >>>>> description field. >>>>> 3) Several users propose fixes. Finally one is accepted as "The Fix" >>>>> and is attached to the Bugzilla bug id. >>>>> 4) Sponsor accepts fix, integrates fix into JDK at 6000000, closes >>>>> the >>>>> bugzilla bug as "SUNBUG", updates the Whiteboard with >>>>> "sunbug=6000000". >>>>> >>>>> Does that correspond to what you're thinking? >>>>> >>>> Not quite. The SUNBUG resolution value is intended for the case of a >>>> Bugzilla bug filed against a component whose bugs are only being >>>> tracked >>>> in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is >>>> more >>>> generally useful. I think your scenario would work better as: >>>> >>>> 1) Internal user has previously filed Bugtraq id 6000000. >>>> 2) External user(s) wants to fix it, so they stake their claim in >>>> Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the >>>> bug's whiteboard. >>>> 3) Several users propose fixes. Finally one is accepted as "The Fix" >>>> and is attached to the Bugzilla bug. >>>> 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and >>>> closes the bug as FIXDELIVERED/FIXED. >>>> >>> Minor nit. When the fix is put into one of the gates, the fix goes >>> to "fix >>> available" in bugtraq. It's the gatekeepers who mark as Fix Delivered. >>> This means the sponsor must watch for the change to hit the MASTER >>> and then >>> remember to move it to FIXDELIVERED, or else the gatekeepers must >>> realize >>> that he has to update both. Or just mark as FIXDELIVERED when it >>> goes into >>> one of the GATES? That'll be confusing. >>> >>> Until we get Bugtraq/Bugzilla linked, this does require someone >>> duplicate >>> the states in both the Bugzilla/Bugster bugids. That's something to >>> address >>> in the sponsor document. >>> >>> >>>> On further thought I'm not going to add a "claim your bug" step just >>>> yet, >>>> the possibility of which I mentioned last night in response to Neal's >>>> comment. >>>> >>> If people are following Section 2 ("discuss your intended change"), >>> this >>> shouldn't be necessary. >>> >>> Brad >>> From Alan.Bateman at Sun.COM Mon Feb 23 19:28:33 2009 From: Alan.Bateman at Sun.COM (Alan Bateman) Date: Mon, 23 Feb 2009 19:28:33 +0000 Subject: [Fwd: Re: Request for comments: New Bugzilla-based contribution process] In-Reply-To: <49A2EB8B.2080305@sun.com> References: <49A2D96C.1090609@sun.com> <49A2EB8B.2080305@sun.com> Message-ID: <49A2F8E1.6040109@sun.com> Brad Wetmore wrote: > : > > So how do people outside Sun figure if this status applies to the JDK7 > or 6uX subCR from the bugs.sun.com page? The "Release Fixed" field is supposed to list the releases. Here's an example: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6571589 There seems to be something broken with the job that transfers the bug updates to bug.sun.com at the moment. I don't know if this explains why 6622432 isn't showing the correct release information. Hopefully it will be fixed soon. -Alan. From mr at sun.com Mon Feb 23 21:29:09 2009 From: mr at sun.com (Mark Reinhold) Date: Mon, 23 Feb 2009 13:29:09 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: bradford.wetmore@sun.com; Sat, 21 Feb 2009 14:25:11 CST; <49A06327.9090800@sun.com> Message-ID: <20090223212909.C9E8E28CFF2@eggemoggin.niobe.net> > Date: Sat, 21 Feb 2009 14:25:11 -0600 > From: bradford.wetmore at sun.com > Mark wrote: >> Brad wrote: >>> but for now we're just using Bugzilla for >>> accepting contributions for bugs that already have bugids in >>> Bugtraq/Bugster (Sun's internal bug tracking system). >> >> Well, not exactly. Contributors are also welcome to submit patches for >> bugs or RFEs that do not already have corresponding Sun bug ids. > > Good to know, I hadn't grasped that subtlety. Maybe that could be > called out a little more in Section 1? Done. >> ... >> >> Not quite. The SUNBUG resolution value is intended for the case of a >> Bugzilla bug filed against a component whose bugs are only being tracked >> in Sun's internal system. The "sunbug=xxxxxxx" whiteboard entry is more >> generally useful. I think your scenario would work better as: >> >> 1) Internal user has previously filed Bugtraq id 6000000. >> 2) External user(s) wants to fix it, so they stake their claim in >> Bugzilla (Bugzilla id 100000), adding "sunbug=6000000" to the >> bug's whiteboard. >> 3) Several users propose fixes. Finally one is accepted as "The Fix" >> and is attached to the Bugzilla bug. >> 4) Sponsor evaluates fix, integrates it into the JDK at 6000000, and >> closes the bug as FIXDELIVERED/FIXED. > > Minor nit. When the fix is put into one of the gates, the fix goes to > "fix available" in bugtraq. It's the gatekeepers who mark as Fix > Delivered. This means the sponsor must watch for the change to hit the > MASTER and then remember to move it to FIXDELIVERED, or else the > gatekeepers must realize that he has to update both. Or just mark as > FIXDELIVERED when it goes into one of the GATES? That'll be confusing. I agree. The simplest thing is probably for a sponsor to set the Bugzilla bug's state to FIXAVAILABLE and then later change it to FIXDELIVERED when corresponding Sun bug is updated to that state. > Until we get Bugtraq/Bugzilla linked, this does require someone > duplicate the states in both the Bugzilla/Bugster bugids. That's > something to address in the sponsor document. Agreed. - Mark From mr at sun.com Mon Feb 23 22:17:46 2009 From: mr at sun.com (Mark Reinhold) Date: Mon, 23 Feb 2009 14:17:46 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: volker.simonis@gmail.com; Fri, 20 Feb 2009 12:33:29 +0100; Message-ID: <20090223221746.6900628CFF2@eggemoggin.niobe.net> > Date: Fri, 20 Feb 2009 12:33:29 +0100 > From: volker.simonis at gmail.com > I'm really happy that the Bugzilla is finally up and running. There is > however one point, which hasn't been addressed until now. It is > already hard to find all the information which belongs to a bug or > changeset. The easy way is from changeset to bug, but the other way > round, from Bug to changeset is already harder, because not every bug > links to the corresponding changeset. Not to mention the webrevs and > the discussions about the webrevs which happened on the mailing list > (see [1] for a previous discussion on this topic). > > Now we get just two more system, the Bugzilla bug tracker and the > Community Code Review site [2]. While this is good thing in general, > how can we ensure that not only the bugzilla entry links to the Sun > bug via the "sunbug" entry, but also the Sun bug links back to the > corresponding Bugzilla entry. And how can we ensure to have a link > from the changelist and/or from the bug to the codereview? The > Bugzilla instance offers the great opportunity that discussions about > a webrev can take place in the open, inside Bugzilla and are preserved > there together with the bug. On the other hand, this hides the > discussions about webrevs from the lists. I don't know Bugzilla, but > perhaps it is possible to forward all changes of bugs from a certain > category(e.g. hotspot), to the corresponding mailing list? > > What are your opinions about how we can get a consistent view of all > the information belonging to a bug? You raise some very good points here. Until the Semantic Web becomes a reality, however, and we all start writing all our documents in perfectly cross-linked XML, I'm afraid the best we can do is identify reasonable tools and practices to help us live with our ever-growing tangled web of documents. As Dmitri suggested later on, automating the cross-linkage of bug reports and changesets should be straightforward and is something we should look into. Linking Sun bugs back to Bugzilla bugs can also be automated, by scanning Bugzilla bugs for sunbug= properties and planting corresponding reverse links in the Sun bug database. Linking code reviews on cr.openjdk.java.net to, and from, the bug databases should be possible with a bit of work. If people consistently name their top-level review directories with bug numbers then it's easy; if not then we'll have to come up with some other way to convey that information. The harder problem is e-mail. We can encourage people to use Bugzilla comments, but the e-mail habit runs strong and deep -- especially within Sun -- so that's likely to prove an uphill battle. Fortunately Google is pretty good at looking for contiguous strings of digits; I'm afraid that's the best solution that I know of in the near term. In the longer term it'd be nice to have a tool like Review Board set up for code reviews, but that's not something we'll have time for in the next few months. FYI I've created a few (Bugzilla!) bugs to capture the linkage ideas that could be implemented near-term [1]. - Mark [1] https://bugs.openjdk.java.net/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=web&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= From mr at sun.com Mon Feb 23 22:21:42 2009 From: mr at sun.com (Mark Reinhold) Date: Mon, 23 Feb 2009 14:21:42 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: gnu_andrew@member.fsf.org; Fri, 20 Feb 2009 16:21:30 GMT; <17c6771e0902200821w7f08c441o15153394acd48164@mail.gmail.com> Message-ID: <20090223222142.7B37028CFF2@eggemoggin.niobe.net> > Date: Fri, 20 Feb 2009 16:21:30 +0000 > From: Andrew John Hughes > ... > > Can we make that a bug watcher mailing list (singular)? We already > have a ridiculous number of lists, doubling that for watching bugs is > going to make things even crazier. Brad is in the process of setting up a single "watch-all" watcher account in Bugzilla, so if you really want to see every update then you can follow that. There will also be per-product watch lists, e.g., "watch-hotspot" for all HotSpot bugs, but at the moment those are less interesting since at the moment most (all?) products only have an "other" component. - Mark From Weijun.Wang at Sun.COM Tue Feb 24 00:14:43 2009 From: Weijun.Wang at Sun.COM (Max (Weijun) Wang) Date: Tue, 24 Feb 2009 08:14:43 +0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <20090223221746.6900628CFF2@eggemoggin.niobe.net> References: <20090223221746.6900628CFF2@eggemoggin.niobe.net> Message-ID: <480D793A-1E4A-475D-B2D1-034317922876@sun.com> > > The harder problem is e-mail. We can encourage people to use Bugzilla > comments, but the e-mail habit runs strong and deep -- especially > within > Sun -- so that's likely to prove an uphill battle. Fortunately Google > is pretty good at looking for contiguous strings of digits; I'm afraid > that's the best solution that I know of in the near term. Is it easy to create virtual mail addresses like bug0000001 at openjdk.java.net ? It can be included in CC of watch alerts. If I reply all to the watch alert mail, then my words can be automatically added into the discuss thread. Max From Dalibor.Topic at Sun.COM Tue Feb 24 00:43:01 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Tue, 24 Feb 2009 01:43:01 +0100 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: <480D793A-1E4A-475D-B2D1-034317922876@sun.com> References: <20090223221746.6900628CFF2@eggemoggin.niobe.net> <480D793A-1E4A-475D-B2D1-034317922876@sun.com> Message-ID: <49A34295.3070908@sun.com> Max (Weijun) Wang wrote: >> >> The harder problem is e-mail. We can encourage people to use Bugzilla >> comments, but the e-mail habit runs strong and deep -- especially within >> Sun -- so that's likely to prove an uphill battle. Fortunately Google >> is pretty good at looking for contiguous strings of digits; I'm afraid >> that's the best solution that I know of in the near term. > > Is it easy to create virtual mail addresses like > bug0000001 at openjdk.java.net? It can be included in CC of watch alerts. > If I reply all to the watch alert mail, then my words can be > automatically added into the discuss thread. Debian uses an e-mail 'based' bug tracker. That has some obvious consequences: http://lists.debian.org/debian-glibc/2008/09/msg00017.html ;) cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From Weijun.Wang at Sun.COM Tue Feb 24 03:10:07 2009 From: Weijun.Wang at Sun.COM (Max (Weijun) Wang) Date: Tue, 24 Feb 2009 11:10:07 +0800 Subject: RFE for webrev: the meaning of -r Message-ID: Hi Jessie Currently, 'webrev -N -r n' creates a diff from rev n to the working directory. Is this really useful? How about output a diff for the changeset rev=n itself? Working on multiple bugs at the moment, I would be very glad to call 'webrev -N -r n' with n=-1,-2,-3... to output a series of webrevs for each changeset I just made. Thanks Max From John.Rose at Sun.COM Tue Feb 24 04:51:09 2009 From: John.Rose at Sun.COM (John Rose) Date: Mon, 23 Feb 2009 20:51:09 -0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: References: Message-ID: On Feb 23, 2009, at 7:10 PM, Max (Weijun) Wang wrote: > Currently, 'webrev -N -r n' creates a diff from rev n to the working > directory. Is this really useful? How about output a diff for the > changeset rev=n itself? It's useful if people don't want to commit their changes before reviewing. (Actually, I use mq to manage my changes, and it does pseudo-commits.) > Working on multiple bugs at the moment, I would be very glad to call > 'webrev -N -r n' with n=-1,-2,-3... to output a series of webrevs > for each changeset I just made. The mercurial way to say this sort of thing is 123:124, where the numbers name two revisions. Perhaps that can be integrated into webrev, although it would touch a couple dozen lines. Best, -- John From Weijun.Wang at Sun.COM Tue Feb 24 04:56:41 2009 From: Weijun.Wang at Sun.COM (Max (Weijun) Wang) Date: Tue, 24 Feb 2009 12:56:41 +0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: References: Message-ID: On Feb 24, 2009, at 12:51 PM, John Rose wrote: > On Feb 23, 2009, at 7:10 PM, Max (Weijun) Wang wrote: > >> Currently, 'webrev -N -r n' creates a diff from rev n to the >> working directory. Is this really useful? How about output a diff >> for the changeset rev=n itself? > > It's useful if people don't want to commit their changes before > reviewing. '-N' itself is useful, but I cannot see what the benefit '-N -r n' is. Wrapping several changes into a single webrev? > (Actually, I use mq to manage my changes, and it does pseudo- > commits.) Me too. I qgoto a patch and call 'webrev -N -r -2' to create a webrev now. > > >> Working on multiple bugs at the moment, I would be very glad to >> call 'webrev -N -r n' with n=-1,-2,-3... to output a series of >> webrevs for each changeset I just made. > > The mercurial way to say this sort of thing is 123:124, where the > numbers name two revisions. This looks better. Thanks Max > Perhaps that can be integrated into webrev, although it would touch > a couple dozen lines. > > Best, > -- John From John.Rose at Sun.COM Tue Feb 24 05:05:46 2009 From: John.Rose at Sun.COM (John Rose) Date: Mon, 23 Feb 2009 21:05:46 -0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: References: Message-ID: On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: > Me too. I qgoto a patch and call 'webrev -N -r -2' to create a > webrev now. Well, that's about what I do, except I have it merge up all my queued changes sometimes. I sometimes have used a wrapper script which finds base revision of the queue like this: > diffbase=$(hg log --rev qparent --template '{rev}') > ... > webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... Saying "webrev -N -r qbase:qtip" could make sense... -- John From Jean-Christophe.Collet at Sun.COM Tue Feb 24 14:57:24 2009 From: Jean-Christophe.Collet at Sun.COM (Jean-Christophe Collet) Date: Tue, 24 Feb 2009 15:57:24 +0100 Subject: RFE for webrev: the meaning of -r In-Reply-To: References: Message-ID: <49A40AD4.1070002@sun.com> I'll see what I can do In the meantime may I suggest you give jHg a try (http://sunweb.swiss/~jccollet/jHg/ ) It's a java tool I wrote that is much more flexible than the webrev script. I'm actually considering building a NetBeans module based on it. John Rose wrote: > On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: > >> Me too. I qgoto a patch and call 'webrev -N -r -2' to create a webrev >> now. > > Well, that's about what I do, except I have it merge up all my queued > changes sometimes. > > I sometimes have used a wrapper script which finds base revision of > the queue like this: > >> diffbase=$(hg log --rev qparent --template '{rev}') >> ... >> webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... > > Saying "webrev -N -r qbase:qtip" could make sense... > > -- John From Jonathan.Gibbons at Sun.COM Tue Feb 24 15:21:22 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Tue, 24 Feb 2009 07:21:22 -0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: <49A40AD4.1070002@sun.com> References: <49A40AD4.1070002@sun.com> Message-ID: Neat looking tool. Would it be too much of a stretch to have the tool optionally publish the webrev to a remote location such as the new code review server? -- Jon On Feb 24, 2009, at 6:57 AM, Jean-Christophe Collet wrote: > I'll see what I can do > In the meantime may I suggest you give jHg a try (http://sunweb.swiss/~jccollet/jHg/ > ) > It's a java tool I wrote that is much more flexible than the webrev > script. > I'm actually considering building a NetBeans module based on it. > > John Rose wrote: >> On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: >> >>> Me too. I qgoto a patch and call 'webrev -N -r -2' to create a >>> webrev now. >> >> Well, that's about what I do, except I have it merge up all my >> queued changes sometimes. >> >> I sometimes have used a wrapper script which finds base revision of >> the queue like this: >> >>> diffbase=$(hg log --rev qparent --template '{rev}') >>> ... >>> webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... >> >> Saying "webrev -N -r qbase:qtip" could make sense... >> >> -- John > From Jean-Christophe.Collet at Sun.COM Tue Feb 24 15:37:17 2009 From: Jean-Christophe.Collet at Sun.COM (Jean-Christophe Collet) Date: Tue, 24 Feb 2009 16:37:17 +0100 Subject: RFE for webrev: the meaning of -r In-Reply-To: References: <49A40AD4.1070002@sun.com> Message-ID: <49A4142D.5070901@sun.com> Jonathan Gibbons wrote: > Neat looking tool. > > Would it be too much of a stretch to have the tool optionally publish > the webrev to a remote location > such as the new code review server? > Good point. I'll try to do that as soon as I get some time > -- Jon > > On Feb 24, 2009, at 6:57 AM, Jean-Christophe Collet wrote: > >> I'll see what I can do >> In the meantime may I suggest you give jHg a try >> (http://sunweb.swiss/~jccollet/jHg/ ) >> It's a java tool I wrote that is much more flexible than the webrev >> script. >> I'm actually considering building a NetBeans module based on it. >> >> John Rose wrote: >>> On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: >>> >>>> Me too. I qgoto a patch and call 'webrev -N -r -2' to create a >>>> webrev now. >>> >>> Well, that's about what I do, except I have it merge up all my >>> queued changes sometimes. >>> >>> I sometimes have used a wrapper script which finds base revision of >>> the queue like this: >>> >>>> diffbase=$(hg log --rev qparent --template '{rev}') >>>> ... >>>> webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... >>> >>> Saying "webrev -N -r qbase:qtip" could make sense... >>> >>> -- John >> > From Jonathan.Gibbons at Sun.COM Tue Feb 24 19:03:42 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Tue, 24 Feb 2009 11:03:42 -0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: <49A4142D.5070901@sun.com> References: <49A40AD4.1070002@sun.com> <49A4142D.5070901@sun.com> Message-ID: <49A4448E.5000203@sun.com> It would be nice to decouple as much as possible the back end of how to publish the webrev. For example, perhaps the tool could collect basic information such as the bug ID, a description of the change, and the location of the webrev directory, and hand this info off to a back-end script provided by the user. That way we could easily use scripts to write files out to the code review server, to the sa.sfbay server, or any other systems that might come along in future. -- Jon Jean-Christophe Collet wrote: > Jonathan Gibbons wrote: >> Neat looking tool. >> >> Would it be too much of a stretch to have the tool optionally >> publish the webrev to a remote location >> such as the new code review server? >> > > Good point. I'll try to do that as soon as I get some time > >> -- Jon >> >> On Feb 24, 2009, at 6:57 AM, Jean-Christophe Collet wrote: >> >>> I'll see what I can do >>> In the meantime may I suggest you give jHg a try >>> (http://sunweb.swiss/~jccollet/jHg/ ) >>> It's a java tool I wrote that is much more flexible than the webrev >>> script. >>> I'm actually considering building a NetBeans module based on it. >>> >>> John Rose wrote: >>>> On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: >>>> >>>>> Me too. I qgoto a patch and call 'webrev -N -r -2' to create a >>>>> webrev now. >>>> >>>> Well, that's about what I do, except I have it merge up all my >>>> queued changes sometimes. >>>> >>>> I sometimes have used a wrapper script which finds base revision of >>>> the queue like this: >>>> >>>>> diffbase=$(hg log --rev qparent --template '{rev}') >>>>> ... >>>>> webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... >>>> >>>> Saying "webrev -N -r qbase:qtip" could make sense... >>>> >>>> -- John >>> >> > From Kelly.Ohair at Sun.COM Tue Feb 24 19:25:05 2009 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Tue, 24 Feb 2009 11:25:05 -0800 Subject: RFE for webrev: the meaning of -r In-Reply-To: <49A4448E.5000203@sun.com> References: <49A40AD4.1070002@sun.com> <49A4142D.5070901@sun.com> <49A4448E.5000203@sun.com> Message-ID: <49A44991.2020901@sun.com> And don't forget that button that submits the patch to a build system that verifies the patch works on all platforms and also runs all smoke tests.... ;^) Oh dear, I think I'm supposed to do that... nevermind.... ;^> Now if I can just figure out how my Sunbeam toaster does it.... -kto Jonathan Gibbons wrote: > It would be nice to decouple as much as possible the back end of how to > publish the webrev. > For example, perhaps the tool could collect basic information such as > the bug ID, a description > of the change, and the location of the webrev directory, and hand this > info off to a back-end > script provided by the user. That way we could easily use scripts to > write files out to the > code review server, to the sa.sfbay server, or any other systems that > might come along in > future. > > -- Jon > > Jean-Christophe Collet wrote: >> Jonathan Gibbons wrote: >>> Neat looking tool. >>> >>> Would it be too much of a stretch to have the tool optionally >>> publish the webrev to a remote location >>> such as the new code review server? >>> >> >> Good point. I'll try to do that as soon as I get some time >> >>> -- Jon >>> >>> On Feb 24, 2009, at 6:57 AM, Jean-Christophe Collet wrote: >>> >>>> I'll see what I can do >>>> In the meantime may I suggest you give jHg a try >>>> (http://sunweb.swiss/~jccollet/jHg/ ) >>>> It's a java tool I wrote that is much more flexible than the webrev >>>> script. >>>> I'm actually considering building a NetBeans module based on it. >>>> >>>> John Rose wrote: >>>>> On Feb 23, 2009, at 8:56 PM, Max (Weijun) Wang wrote: >>>>> >>>>>> Me too. I qgoto a patch and call 'webrev -N -r -2' to create a >>>>>> webrev now. >>>>> >>>>> Well, that's about what I do, except I have it merge up all my >>>>> queued changes sometimes. >>>>> >>>>> I sometimes have used a wrapper script which finds base revision of >>>>> the queue like this: >>>>> >>>>>> diffbase=$(hg log --rev qparent --template '{rev}') >>>>>> ... >>>>>> webrev -m -N -i $info -o $temp -r $diffbase -p "$parent" ... >>>>> >>>>> Saying "webrev -N -r qbase:qtip" could make sense... >>>>> >>>>> -- John >>>> >>> >> > From Dalibor.Topic at Sun.COM Tue Feb 24 22:16:41 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Tue, 24 Feb 2009 23:16:41 +0100 Subject: OpenJDK Forum: Contributing into OpenJDK 6 Message-ID: <49A471C9.2010101@sun.com> Hi everyone, I'd like to carry a bit of the great spirit of discussions from FOSDEM forward, so we're trying out something new: OpenJDK Forum Date/Time: Friday Feb. 27, 2008 8 AM Pacific, 1600 GMT, 5 PM Germany Subject: Contributing into OpenJDK 6 Call Host: Dalibor Topic Expected Participants: * Emily Chang * Joe Darcy * Mark Reinhold * Dalibor Topic + members of discuss at openjdk and jdk6-dev at openjdk mailing lists interested in the new Bugzilla-based contribution process and 'push' rights for OpenJDK 6 repositories. Synopsis: We will cover the new contribution process. We'll start by reviewing the new Bugzilla-based contribution process and expectations around establishing authorship (i.e. 'push') rights for the writable OpenJDK 6 repositories. We will then switch to open discussion mode to hear people's questions, concerns, and suggestions on the subject matter. The call will be recorded, and the recording will be made available after the call - in a free format, of course! Dial in numbers: Passcode: 5817876 Speed dial extension for developers inside Sun: x44414 Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0463 AUSTRALIA ADELAIDE: 61-8-8121-4868 1-800-249-288 AUSTRALIA BRISBANE: 61-7-3102-0970 1-800-249-288 AUSTRALIA CANBERRA: 61-2-6100-1970 1-800-249-288 AUSTRALIA MELBOURNE: 61-3-9010-7739 1-800-249-288 AUSTRALIA PERTH: 61-8-9467-5249 1-800-249-288 AUSTRALIA SYDNEY: 61-2-8205-8125 1-800-249-288 AUSTRIA 43-1-92-86-506 0800-005-029 BELGIUM 32-1-150-0314 0800-4-8680 BRAZIL 0800-7610674 CHILE 1230-020-2867 CHINA* 86-400-810-4766 10800-712-1433 10800-120-1433 COLOMBIA 01800-9-156430 CZECH REPUBLIC 420-2-25-98-56-54 800-700-173 DENMARK 45-7014-0280 8088-6132 ESTONIA 800-011-1089 FINLAND Land Line: 106-33-146 0-800-1-10100 FINLAND Mobile: 09-106-33-146 0-800-1-10100 FRANCE LYON: 33-4-26-69-12-81 080-563-9647 FRANCE MARSEILLE: 33-4-86-06-00-81 080-563-9647 FRANCE PARIS: 33-1-70-70-74-20 080-563-9647 GERMANY 49-69-2222-2566 0800-000-3441 GREECE 30-80-1-100-0683 00800-12-6973 HONG KONG 852-2286-5731 800-930-705 HUNGARY 06-800-18013 INDIA 000-800-852-1266 INDONESIA 001-803-011-3787 IRELAND 353-1-247-5253 1800-932-145 ISRAEL 1-80-9214916 ITALY 39-02-3600-3642 800-986-570 JAPAN OSAKA: 81-6-7739-4769 0034-800-400828 JAPAN TOKYO: 81-3-5539-5189 0034-800-400828 LATVIA 8000-3025 LUXEMBOURG 352-27-000-1360 MALAYSIA 1-800-80-2812 MEXICO 001-866-627-0574 NETHERLANDS 31-20-718-8533 0800-020-1392 NEW ZEALAND 64-9-970-4769 0800-449-823 NORWAY 47-21-59-00-59 800-15414 PANAMA 011-001-800-5072129 PERU 0800-53733 PHILIPPINES 63-2-858-3715 POLAND 00-800-1212021 PORTUGAL 8008-14061 RUSSIA 8-10-8002-9683011 SINGAPORE 65-6883-9228 800-120-4662 SLOVAK REPUBLIC 421-2-322-422-21 SOUTH AFRICA 080-09-80416 SOUTH KOREA 82-2-6744-1081 00798-14800-6860 SPAIN 34-91-414-62-98 800-099-810 SWEDEN 46-8-505-78-524 0200-890-106 SWITZERLAND 41-44-580-4389 0800-001-523 TAIWAN 886-2-2795-7377 00801-137-766 THAILAND 001-800-1206-65656 UNITED KINGDOM BIRMINGHAM: 44-121-210-9021 0808-238-6025 UNITED KINGDOM GLASGOW: 44-141-202-3221 0808-238-6025 UNITED KINGDOM LEEDS: 44-113-301-2121 0808-238-6025 UNITED KINGDOM LONDON: 44-20-7075-3246 0808-238-6025 UNITED KINGDOM MANCHESTER: 44-161-601-1421 0808-238-6025 URUGUAY 000-413-598-3415 USA 1-203-418-3122 866-692-3163 VENEZUELA 0800-1-00-3733 cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From volker.simonis at gmail.com Wed Feb 25 15:52:16 2009 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 25 Feb 2009 16:52:16 +0100 Subject: OpenJDK Forum: Contributing into OpenJDK 6 In-Reply-To: <49A471C9.2010101@sun.com> References: <49A471C9.2010101@sun.com> Message-ID: Hi, sounds very interesting! I'll try to join the discussion on Friday. One point of special interest for us would be if SCSL licensees (and here especially the ones which signed the "commercial use" amendment) will be able to submit under the SCSL into this repository. From our point of view the SCSL is a true superset of the SCA and should cover everything covered by the SCA. We have also discussed this with Onno in the past who shared our point of view in this point, but as far as I know there has never been an "official" statement with regard to this topic. It would be nice if somebody can have a look at this, because I think it would considerably simplify the contribution process for certain SCSL licensees. With best regards, Volker On 2/24/09, Dalibor Topic wrote: > Hi everyone, > > I'd like to carry a bit of the great spirit of discussions > from FOSDEM forward, so we're trying out something new: > > OpenJDK Forum > > Date/Time: Friday Feb. 27, 2008 8 AM Pacific, 1600 GMT, 5 PM Germany > > Subject: Contributing into OpenJDK 6 > > Call Host: Dalibor Topic > > Expected Participants: > > * Emily Chang > * Joe Darcy > * Mark Reinhold > * Dalibor Topic > > + members of discuss at openjdk and jdk6-dev at openjdk > mailing lists interested in the new Bugzilla-based > contribution process and 'push' rights for > OpenJDK 6 repositories. > > Synopsis: > > We will cover the new contribution process. We'll start by > reviewing the new Bugzilla-based contribution process and > expectations around establishing authorship (i.e. 'push') > rights for the writable OpenJDK 6 repositories. > > We will then switch to open discussion mode to hear people's > questions, concerns, and suggestions on the subject matter. > > The call will be recorded, and the recording will be made > available after the call - in a free format, of course! > > Dial in numbers: > > Passcode: 5817876 > > Speed dial extension for developers inside Sun: x44414 > > Country Toll Numbers Freephone/Toll Free Number > > ARGENTINA 0800-777-0463 > AUSTRALIA ADELAIDE: 61-8-8121-4868 1-800-249-288 > AUSTRALIA BRISBANE: 61-7-3102-0970 1-800-249-288 > AUSTRALIA CANBERRA: 61-2-6100-1970 1-800-249-288 > AUSTRALIA MELBOURNE: 61-3-9010-7739 1-800-249-288 > AUSTRALIA PERTH: 61-8-9467-5249 1-800-249-288 > AUSTRALIA SYDNEY: 61-2-8205-8125 1-800-249-288 > AUSTRIA 43-1-92-86-506 0800-005-029 > BELGIUM 32-1-150-0314 0800-4-8680 > BRAZIL 0800-7610674 > CHILE 1230-020-2867 > CHINA* 86-400-810-4766 10800-712-1433 > 10800-120-1433 > COLOMBIA 01800-9-156430 > CZECH REPUBLIC 420-2-25-98-56-54 800-700-173 > DENMARK 45-7014-0280 8088-6132 > ESTONIA 800-011-1089 > FINLAND Land Line: 106-33-146 0-800-1-10100 > FINLAND Mobile: 09-106-33-146 0-800-1-10100 > FRANCE LYON: 33-4-26-69-12-81 080-563-9647 > FRANCE MARSEILLE: 33-4-86-06-00-81 080-563-9647 > FRANCE PARIS: 33-1-70-70-74-20 080-563-9647 > GERMANY 49-69-2222-2566 0800-000-3441 > GREECE 30-80-1-100-0683 00800-12-6973 > HONG KONG 852-2286-5731 800-930-705 > HUNGARY 06-800-18013 > INDIA 000-800-852-1266 > INDONESIA 001-803-011-3787 > IRELAND 353-1-247-5253 1800-932-145 > ISRAEL 1-80-9214916 > ITALY 39-02-3600-3642 800-986-570 > JAPAN OSAKA: 81-6-7739-4769 0034-800-400828 > JAPAN TOKYO: 81-3-5539-5189 0034-800-400828 > LATVIA 8000-3025 > LUXEMBOURG 352-27-000-1360 > MALAYSIA 1-800-80-2812 > MEXICO 001-866-627-0574 > NETHERLANDS 31-20-718-8533 0800-020-1392 > NEW ZEALAND 64-9-970-4769 0800-449-823 > NORWAY 47-21-59-00-59 800-15414 > PANAMA 011-001-800-5072129 > PERU 0800-53733 > PHILIPPINES 63-2-858-3715 > POLAND 00-800-1212021 > PORTUGAL 8008-14061 > RUSSIA 8-10-8002-9683011 > SINGAPORE 65-6883-9228 800-120-4662 > SLOVAK REPUBLIC 421-2-322-422-21 > SOUTH AFRICA 080-09-80416 > SOUTH KOREA 82-2-6744-1081 00798-14800-6860 > SPAIN 34-91-414-62-98 800-099-810 > SWEDEN 46-8-505-78-524 0200-890-106 > SWITZERLAND 41-44-580-4389 0800-001-523 > TAIWAN 886-2-2795-7377 00801-137-766 > THAILAND 001-800-1206-65656 > UNITED KINGDOM BIRMINGHAM: 44-121-210-9021 0808-238-6025 > UNITED KINGDOM GLASGOW: 44-141-202-3221 0808-238-6025 > UNITED KINGDOM LEEDS: 44-113-301-2121 0808-238-6025 > UNITED KINGDOM LONDON: 44-20-7075-3246 0808-238-6025 > UNITED KINGDOM MANCHESTER: 44-161-601-1421 0808-238-6025 > URUGUAY 000-413-598-3415 > USA 1-203-418-3122 866-692-3163 > VENEZUELA 0800-1-00-3733 > > > cheers, > dalibor topic > > -- > ******************************************************************* > Dalibor Topic Tel: (+49 40) 23 646 738 > Java F/OSS Ambassador AIM: robiladonaim > Sun Microsystems GmbH Mobile: (+49 177) 2664 192 > Nagelsweg 55 http://openjdk.java.net > D-20097 Hamburg mailto:Dalibor.Topic at sun.com > Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten > Amtsgericht M?nchen: HRB 161028 > Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer > Vorsitzender des Aufsichtsrates: Martin H?ring > > > From gnu_andrew at member.fsf.org Wed Feb 25 21:11:25 2009 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Wed, 25 Feb 2009 21:11:25 +0000 Subject: FOSDEM 2009: First Talk Recording Now Available Message-ID: <17c6771e0902251311u23b6c5e5r2e47dba286ba6593@mail.gmail.com> You'll find Mark Reinhold's talk on 'The State of OpenJDK7' here: http://www.archive.org/details/fosdem_2009_free_java_the_state_of_openjdk_7 It's available under the Creative Commons Attribution No-Derivative license (http://creativecommons.org/licenses/by-nd/2.0/uk/). Please feel free to distribute copies under those terms. Thanks to Mark Reinhold for allowing this to be made available. He also gave the all clear for the Project Jigsaw talk which will be available soon. For a more retro talk, Andrew Haley's talk given at the University of Sheffield last year is also available (can't remember if I already mentioned this or not): http://www.archive.org/details/freedom_and_free_java This was part of Sun's Campus Ambassador scheme. Again, my thanks to Andrew for allowing this to be recorded and published. If there are any issues with the publication of these talks, please contact me ASAP. More to come in time and with appropriate permissions, -- 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 Feb 26 21:10:54 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 26 Feb 2009 13:10:54 -0800 Subject: Request for comments: New Bugzilla-based contribution process In-Reply-To: mr@sun.com; Wed, 18 Feb 2009 20:49:23 PST; <20090219044923.DAB37CFD3@callebaut.niobe.net> Message-ID: <20090226211055.04BC628E0EE@eggemoggin.niobe.net> Thanks to everyone who commented on the new contribution process. It has now replaced the old process, here: http://openjdk.java.net/contribute - Mark From mr at sun.com Thu Feb 26 22:21:08 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 26 Feb 2009 14:21:08 -0800 Subject: FYI: JDK 7 process discussion on jdk7-dev Message-ID: <20090226222108.3AD5D28E0EE@eggemoggin.niobe.net> I've started a thread to review the first draft of the JDK 7 process document. Please send comments to the jdk7-dev list. - Mark From mr at sun.com Thu Feb 26 22:21:08 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 26 Feb 2009 14:21:08 -0800 Subject: FYI: JDK 7 process discussion on jdk7-dev Message-ID: <20090226222108.3AD5D28E0EE@eggemoggin.niobe.net> I've started a thread to review the first draft of the JDK 7 process document. Please send comments to the jdk7-dev list. - Mark -------------- next part -------------- An embedded message was scrubbed... From: Mark Reinhold Subject: Request for comments: JDK 7 Development Process Date: Thu, 26 Feb 2009 14:12:25 -0800 Size: 1101 URL: From Dalibor.Topic at Sun.COM Fri Feb 27 00:52:37 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 27 Feb 2009 01:52:37 +0100 Subject: Request for comments: New Bugzilla-based sponsoring process Message-ID: <49A73955.8050409@sun.com> Good morning everyone, thanks to Mark and the contributors on this mailing list we now have a new Bugzilla-based contribution process [1]. It's time to define the Bugzilla-based sponsoring process, thereby complementing the new contribution process. I've posted a first draft [2] on our extremely easy to upload to code-review server (thanks, Tim!). Comments are very welcome. cheers, dalibor tpoic [1] http://openjdk.java.net/contribute/ [2] http://cr.openjdk.java.net/~robilad/sponsoring.html -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring From John.Coomes at sun.com Fri Feb 27 01:47:51 2009 From: John.Coomes at sun.com (John Coomes) Date: Thu, 26 Feb 2009 17:47:51 -0800 Subject: Request for comments: New Bugzilla-based sponsoring process In-Reply-To: <49A73955.8050409@sun.com> References: <49A73955.8050409@sun.com> Message-ID: <18855.17991.812626.848111@sun.com> Dalibor Topic (Dalibor.Topic at Sun.COM) wrote: > Good morning everyone, > > thanks to Mark and the contributors on this mailing list we now > have a new Bugzilla-based contribution process [1]. It's time > to define the Bugzilla-based sponsoring process, thereby > complementing the new contribution process. > > I've posted a first draft [2] on our extremely easy to upload to > code-review server (thanks, Tim!). Comments are very welcome. Hi Dalibor, Looks good; I have a couple of comments. First, section "2. Link the contribution back to a Sun bug" includes this: The Sun bug's description can just be a hyperlink straight to the Bugzilla bug. Using the URL as the description isn't very useful, since bug descriptions show up in all kinds of reports and in searches of Sun's internal bug database. I think both bugs should have the same description; the hyperlink to the bugzilla bug can be used as the Sun bug evaluation. Second, we include bug numbers in changeset comments. Should we use the Sun bug id, the mozilla bug id, both? -John From John.Coomes at sun.com Fri Feb 27 05:47:08 2009 From: John.Coomes at sun.com (John Coomes) Date: Thu, 26 Feb 2009 21:47:08 -0800 Subject: Request for comments: New Bugzilla-based sponsoring process In-Reply-To: <18855.17991.812626.848111@sun.com> References: <49A73955.8050409@sun.com> <18855.17991.812626.848111@sun.com> Message-ID: <18855.32348.434326.784099@sun.com> I (John.Coomes at sun.com) wrote: > Dalibor Topic (Dalibor.Topic at Sun.COM) wrote: > > Good morning everyone, > > > > thanks to Mark and the contributors on this mailing list we now > > have a new Bugzilla-based contribution process [1]. It's time > > to define the Bugzilla-based sponsoring process, thereby > > complementing the new contribution process. > > > > I've posted a first draft [2] on our extremely easy to upload to > > code-review server (thanks, Tim!). Comments are very welcome. > > Hi Dalibor, > > Looks good; I have a couple of comments. > > First, section "2. Link the contribution back to a Sun bug" includes > this: > > The Sun bug's description can just be a hyperlink straight to > the Bugzilla bug. > > Using the URL as the description isn't very useful, since bug > descriptions show up in all kinds of reports and in searches of Sun's > internal bug database. I think both bugs should have the same > description; the hyperlink to the bugzilla bug can be used as the Sun > bug evaluation. Uh, nevermind this first comment. You wrote "description," but I read it as "synopsis." Using the URL for the description is fine. > Second, we include bug numbers in changeset comments. Should we use > the Sun bug id, the mozilla bug id, both? This I'd still like to know. Finally, since it's a manual process, it's inevitable that some mozilla & sun interal bug states will diverge. It'd be nice if there was a simple way to list bugs that are not in sync, by engineer and/or by category. -John From Xiomara.Jayasena at Sun.COM Fri Feb 27 06:31:57 2009 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Thu, 26 Feb 2009 22:31:57 -0800 Subject: JDK 7 build 49 is available at the openjdk.java.net website Message-ID: <49A788DD.1010604@sun.com> The OpenJDK source is available at: http://hg.openjdk.java.net/jdk7/jdk7 http://hg.openjdk.java.net/jdk7/jdk7/rev/aee93a8992d2 The OpenJDK source binary plugs for the promoted JDK 7 build 49 are available under the openjdk http://openjdk.java.net website under Source Code (direct link to bundles: http://download.java.net/openjdk/jdk7) Summary of changes: (The integrator forgot to mark the bugs, so the link is empty for now) http://download.java.net/jdk7/changes/jdk7-b49.html -Xiomara From vmikheev at excelsior-usa.com Fri Feb 27 12:54:07 2009 From: vmikheev at excelsior-usa.com (Vitaly Mikheev) Date: Fri, 27 Feb 2009 18:54:07 +0600 Subject: OpenJDK Forum: Contributing into OpenJDK 6 Message-ID: Hi Volker, >>One point of special interest for us would be if SCSL licensees (and >>here especially the ones which signed the "commercial use" amendment) Thank you for pointing attention to this issue. Excelsior LLC is a SCSL licensee signed the "commercial use" amendment. I confirm that we are very interested in contribution to OpenJDK under SCA. I had some e-mail exchange with Mark but so far we have no progress in it. Regards, --Vitaly > -----Original Message----- > From: discuss-bounces at openjdk.java.net [SMTP:discuss-bounces at openjdk.java.net] On Behalf Of Volker Simonis > Sent: Wednesday, February 25, 2009 9:52 PM > To: Dalibor Topic > Cc: discuss at openjdk.java.net; Emily Chang; jdk6-dev at openjdk.java.net; Joe Darcy > Subject: Re: OpenJDK Forum: Contributing into OpenJDK 6 > > Hi, > > sounds very interesting! I'll try to join the discussion on Friday. > > One point of special interest for us would be if SCSL licensees (and > here especially the ones which signed the "commercial use" amendment) > will be able to submit under the SCSL into this repository. From our > point of view the SCSL is a true superset of the SCA and should cover > everything covered by the SCA. We have also discussed this with Onno > in the past who shared our point of view in this point, but as far as > I know there has never been an "official" statement with regard to > this topic. > > It would be nice if somebody can have a look at this, because I think > it would considerably simplify the contribution process for certain > SCSL licensees. > > With best regards, > Volker > > On 2/24/09, Dalibor Topic wrote: > > Hi everyone, > > > > I'd like to carry a bit of the great spirit of discussions > > from FOSDEM forward, so we're trying out something new: > > > > OpenJDK Forum > > > > Date/Time: Friday Feb. 27, 2008 8 AM Pacific, 1600 GMT, 5 PM Germany > > > > Subject: Contributing into OpenJDK 6 > > > > Call Host: Dalibor Topic > > > > Expected Participants: > > > > * Emily Chang > > * Joe Darcy > > * Mark Reinhold > > * Dalibor Topic > > > > + members of discuss at openjdk and jdk6-dev at openjdk > > mailing lists interested in the new Bugzilla-based > > contribution process and 'push' rights for > > OpenJDK 6 repositories. > > > > Synopsis: > > > > We will cover the new contribution process. We'll start by > > reviewing the new Bugzilla-based contribution process and > > expectations around establishing authorship (i.e. 'push') > > rights for the writable OpenJDK 6 repositories. > > > > We will then switch to open discussion mode to hear people's > > questions, concerns, and suggestions on the subject matter. > > > > The call will be recorded, and the recording will be made > > available after the call - in a free format, of course! > > > > Dial in numbers: > > > > Passcode: 5817876 > > > > Speed dial extension for developers inside Sun: x44414 > > > > Country Toll Numbers Freephone/Toll Free Number > > > > ARGENTINA 0800-777-0463 > > AUSTRALIA ADELAIDE: 61-8-8121-4868 1-800-249-288 > > AUSTRALIA BRISBANE: 61-7-3102-0970 1-800-249-288 > > AUSTRALIA CANBERRA: 61-2-6100-1970 1-800-249-288 > > AUSTRALIA MELBOURNE: 61-3-9010-7739 1-800-249-288 > > AUSTRALIA PERTH: 61-8-9467-5249 1-800-249-288 > > AUSTRALIA SYDNEY: 61-2-8205-8125 1-800-249-288 > > AUSTRIA 43-1-92-86-506 0800-005-029 > > BELGIUM 32-1-150-0314 0800-4-8680 > > BRAZIL 0800-7610674 > > CHILE 1230-020-2867> > > CHINA* 86-400-810-4766 10800-712-1433 > > 10800-120-1433 > > COLOMBIA 01800-9-156430 > > CZECH REPUBLIC 420-2-25-98-56-54 800-700-173 > > DENMARK 45-7014-0280 8088-6132 > > ESTONIA 800-011-1089 > > FINLAND Land Line: 106-33-146 0-800-1-10100 > > FINLAND Mobile: 09-106-33-146 0-800-1-10100 > > FRANCE LYON: 33-4-26-69-12-81 080-563-9647 > > FRANCE MARSEILLE: 33-4-86-06-00-81 080-563-9647 > > FRANCE PARIS: 33-1-70-70-74-20 080-563-9647 > > GERMANY 49-69-2222-2566 0800-000-3441 > > GREECE 30-80-1-100-0683 00800-12-6973 > > HONG KONG 852-2286-5731 800-930-705 > > HUNGARY 06-800-18013 > > INDIA 000-800-852-1266 > > INDONESIA 001-803-011-3787 > > IRELAND 353-1-247-5253 1800-932-145 > > ISRAEL 1-80-9214916 > > ITALY 39-02-3600-3642 800-986-570 > > JAPAN OSAKA: 81-6-7739-4769 0034-800-400828 > > JAPAN TOKYO: 81-3-5539-5189 0034-800-400828 > > LATVIA 8000-3025 > > LUXEMBOURG 352-27-000-1360 > > MALAYSIA 1-800-80-2812 > > MEXICO 001-866-627-0574 > > NETHERLANDS 31-20-718-8533 0800-020-1392 > > NEW ZEALAND 64-9-970-4769 0800-449-823 > > NORWAY 47-21-59-00-59 800-15414 > > PANAMA 011-001-800-5072129 > > PERU 0800-53733 > > PHILIPPINES 63-2-858-3715 > > POLAND 00-800-1212021 > > PORTUGAL 8008-14061 > > RUSSIA 8-10-8002-9683011 > > SINGAPORE 65-6883-9228 800-120-4662 > > SLOVAK REPUBLIC 421-2-322-422-21 > > SOUTH AFRICA 080-09-80416 > > SOUTH KOREA 82-2-6744-1081 00798-14800-6860 > > SPAIN 34-91-414-62-98 800-099-810 > > SWEDEN 46-8-505-78-524 0200-890-106 > > SWITZERLAND 41-44-580-4389 0800-001-523 > > TAIWAN 886-2-2795-7377 00801-137-766 > > THAILAND 001-800-1206-65656 > > UNITED KINGDOM BIRMINGHAM: 44-121-210-9021 0808-238-6025 > > UNITED KINGDOM GLASGOW: 44-141-202-3221 0808-238-6025 > > UNITED KINGDOM LEEDS: 44-113-301-2121 0808-238-6025 > > UNITED KINGDOM LONDON: 44-20-7075-3246 0808-238-6025 > > UNITED KINGDOM MANCHESTER: 44-161-601-1421 0808-238-6025 > > URUGUAY 000-413-598-3415 > > USA 1-203-418-3122 866-692-3163> > > VENEZUELA 0800-1-00-3733 > > > > > > cheers, > > dalibor topic > > > > -- > > ******************************************************************* > > Dalibor Topic Tel: (+49 40) 23 646 738 > > Java F/OSS Ambassador AIM: robiladonaim > > Sun Microsystems GmbH Mobile: (+49 177) 2664 192 > > Nagelsweg 55 http://openjdk.java.net > > D-20097 Hamburg mailto:Dalibor.Topic at sun.com > > Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten > > Amtsgericht Munchen: HRB 161028 > > Geschaftsfuhrer: Thomas Schroder, Wolfgang Engels, Dr. Roland Bomer > > Vorsitzender des Aufsichtsrates: Martin Haring > > > > > > From Dalibor.Topic at Sun.COM Fri Feb 27 15:46:29 2009 From: Dalibor.Topic at Sun.COM (Dalibor Topic) Date: Fri, 27 Feb 2009 16:46:29 +0100 Subject: Updates: OpenJDK Forum: Contributing into OpenJDK 6 In-Reply-To: <49A471C9.2010101@sun.com> References: <49A471C9.2010101@sun.com> Message-ID: <49A80AD5.9080803@sun.com> Dalibor Topic wrote: > Hi everyone, > > I'd like to carry a bit of the great spirit of discussions > from FOSDEM forward, so we're trying out something new: > > OpenJDK Forum Expected Participants: I hope that we'll also be able to have Dmitri Trembovetski and Phil Race join us for the call. Since conference calls may be a somewhat new experience to some of us, here are a couple ground rules: * Please identify yourself by name and location when speaking. At least in theory, we could have more then one Dalibor on the call, for example, and for those of us not familiar with each Dalibor's voice, having a way to pick them apart is useful. * Please address individuals by name when speaking. That helps keep the discussion flowing, without causing confusion who a particular question, remark or idea is addressed to. * Please speak clearly and avoid side conversations and background noise. We'll use the #openjdk IRC channel on irc.oftc.net for side conversations. If you are not familiar with IRC clients, you can run the corresponding web start application at http://openjdk.java.net/irc/ . * Keeping the noise down When you're not speaking, please mute your own line by pressing *6 on your telephone keypad. To unmute press *6 again. * On Sun campus in SCA ? Please join Mark Reinhold in the conference room "Mars Bars" in building 22, second floor. cheers, dalibor topic -- ******************************************************************* Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht M?nchen: HRB 161028 Gesch?ftsf?hrer: Thomas Schr?der, Wolfgang Engels, Dr. Roland B?mer Vorsitzender des Aufsichtsrates: Martin H?ring