From Phil.Race at Sun.COM Tue Mar 3 13:43:15 2009 From: Phil.Race at Sun.COM (Phil Race) Date: Tue, 03 Mar 2009 13:43:15 -0800 Subject: who should use bugzilla ? Message-ID: <49ADA473.6090709@sun.com> Hello Brad and Mark, As you can see from the email below, there's something of an apparent hole in the description of who should use bugzilla. Can we clarify what's supposed to be the process Specifically if you are external to Sun. but have an openjdk user id either because you are a member of an openjdk group (eg 2d, awt), OR because you have an openjdk project, then should you in fact use bugzilla, since you can't use the Sun internal bugster tool ? -phil. -------- Original Message -------- Roman Kennke wrote: >> >> For the cases where where you have a proposed fix, then use bugzilla, for >> the ones you don't submitting each of those tests as a bug report into bugs.sun.com >> is the right thing to do at the moment. > > Ok. The announcement also says 'contributions from those developers > without push permissions'. This is interesting, as it excludes people > like me, who have push access, but I cannot really make use of > bugs.sun.com either. So I will continue to send emails instead. I think the intent is that patches should NOT be sent in email, as bugzilla is now available to track those patches so that they don't get lost in the email and its easier to see where we are WRT to integrating contributions. So you should use bugzilla for submitting patches, even if you ultimately push them. Patches already in process likely don't need to be retrospectively added to bugzilla unless you want to do that. -phil. From martinrb at google.com Wed Mar 4 15:54:53 2009 From: martinrb at google.com (Martin Buchholz) Date: Wed, 4 Mar 2009 15:54:53 -0800 Subject: who should use bugzilla ? In-Reply-To: <49ADA473.6090709@sun.com> References: <49ADA473.6090709@sun.com> Message-ID: <1ccfd1c10903041554r46fb6094h35ae00e3bb24dda3@mail.gmail.com> On Tue, Mar 3, 2009 at 13:43, Phil Race wrote: > Hello Brad and Mark, > Specifically if you are external to Sun. but have an openjdk user id > either because you are a member of an openjdk group (eg 2d, awt), OR > because you have an openjdk project, then should you in fact use > bugzilla, since you can't use the Sun internal bugster tool ? I am waiting for an announcement that would allow me to do my first commit entirely without Sun engineer help. Martin From Tim.Bell at Sun.COM Wed Mar 4 17:52:24 2009 From: Tim.Bell at Sun.COM (Tim Bell) Date: Wed, 04 Mar 2009 17:52:24 -0800 Subject: OpenJDK Community Code Review server rollout In-Reply-To: References: <498A851A.5060605@sun.com> <49999E90.507@sun.com> <499AEA9B.2090506@sun.com> Message-ID: <49AF3058.40006@sun.com> [Moving this thread to web-discuss (at) openjdk.java.net] John Rose wrote: > Thanks! A couple of RFEs: Thanks back. BTW - I owe a lot to Dan Price and the OpenSolaris folks for working out this code review server scheme - what I did was take their layout and hook it up with our db.ojn server and authentication scheme. After we got a bunch of Legal approval and other non-programming issues settled... > You mention webrev on the root page; can we have a link to it there, as > there in your rollout Email? Yes, I will make that information more prominent on the page later tonight. Jessie (Jean-Christophe Collet) has been doing good work on the webrev script lately, so you probably want to be running the latest version: http://blogs.sun.com/jcc/ http://blogs.sun.com/jcc/resource/webrev > The webrevs are not very portable in their expanded browsable state: > There are too many files. I'd like to see an option to upload or > download a *tgz or *zip bundle as a unit. > > It could be fairly simple, with just one bit of magic: Have a private > ".bundles" subdirectory hierarchy with a background script watching it, > like ".trashes". Uploading to ".bundles" would cause the archive file > to be unpacked (relative to top level). Allow both ".bundles" "bundles" > (w/ & w/o leading dot) also, so that the archive files themselves could > be left out in public, for easy anonymous downloading. Good idea, and not so hard to set up. Does anyone else have an opinion on this feature? I will work on getting this up later this week. Thanks for the feedback- Tim > P.S. The old http://webrev.invokedynamic.info/ site did not supply > rsync/scp/sftp, so I forced users to upload single *tgz or *zip files > manually. The virtue of this necessity was that the server uploaded the > bundles as a unit and then unpacked them locally, saving lots of network > handshakes. Yes, that is true, although I don't notice a real bottleneck with the network. I typically start up a 'scp -r' and then go heat up some water for tea... From mr at sun.com Wed Mar 4 20:42:52 2009 From: mr at sun.com (Mark Reinhold) Date: Wed, 04 Mar 2009 20:42:52 -0800 Subject: who should use bugzilla ? In-Reply-To: phil.race@sun.com; Tue, 03 Mar 2009 13:43:15 PST; <49ADA473.6090709@sun.com> Message-ID: <20090305044252.60BCAD06B@callebaut.niobe.net> > Date: Tue, 03 Mar 2009 13:43:15 -0800 > From: phil.race at sun.com > As you can see from the email below, there's something of > an apparent hole in the description of who should use bugzilla. > > Can we clarify what's supposed to be the process > > Specifically if you are external to Sun. but have an openjdk user id > either because you are a member of an openjdk group (eg 2d, awt), OR > because you have an openjdk project, then should you in fact use > bugzilla, since you can't use the Sun internal bugster tool ? In the long run, people such as Roman who have push rights into the JDK 6 and 7 forests -- and in his case have in fact already pushed changes to at least one of those forests, after appropriate review -- should not need to use a special process set up primarily for people who haven't yet earned such rights. Having said that, Roman is completely right to point out that he can't make effective use of bugs.sun.com on his own. There are, moreover, other internal tools, e.g., the code-review robot, that aren't (yet) available to external developers. Until such time as more of our internal tools are externalized, and we use our Bugzilla for all bugs rather than just for contributions from non-Sun developers, I see no harm in using Bugzilla to track changes being proposed by such developers even if they do have push rights into the appropriate forests. If there's general agreement on this then I'll arrange for the warning header on bugs.openjdk.java.net to be modified accordingly. - Mark From Ulf.Zibis at gmx.de Thu Mar 5 03:32:00 2009 From: Ulf.Zibis at gmx.de (Ulf Zibis) Date: Thu, 05 Mar 2009 12:32:00 +0100 Subject: who should use bugzilla ? In-Reply-To: <20090305044252.60BCAD06B@callebaut.niobe.net> References: <20090305044252.60BCAD06B@callebaut.niobe.net> Message-ID: <49AFB830.4040601@gmx.de> Hi all, I also think, that existing tools for externals are very poor, compared e.g. with NetBeans project. Especially on the bug parade I'm missing: - sophisticated search tools - saving search profiles - reopening bugs from external - attaching resources - customising the watch list, e.g. displaying the summary in the list (today only id's are displayed, and you have to open all links, to see what's inside) -Ulf Am 05.03.2009 05:42, Mark Reinhold schrieb: >> Date: Tue, 03 Mar 2009 13:43:15 -0800 >> From: phil.race at sun.com >> > > >> As you can see from the email below, there's something of >> an apparent hole in the description of who should use bugzilla. >> >> Can we clarify what's supposed to be the process >> >> Specifically if you are external to Sun. but have an openjdk user id >> either because you are a member of an openjdk group (eg 2d, awt), OR >> because you have an openjdk project, then should you in fact use >> bugzilla, since you can't use the Sun internal bugster tool ? >> > > In the long run, people such as Roman who have push rights into the JDK 6 > and 7 forests -- and in his case have in fact already pushed changes to > at least one of those forests, after appropriate review -- should not > need to use a special process set up primarily for people who haven't yet > earned such rights. > > Having said that, Roman is completely right to point out that he can't > make effective use of bugs.sun.com on his own. There are, moreover, > other internal tools, e.g., the code-review robot, that aren't (yet) > available to external developers. > > Until such time as more of our internal tools are externalized, and we > use our Bugzilla for all bugs rather than just for contributions from > non-Sun developers, I see no harm in using Bugzilla to track changes > being proposed by such developers even if they do have push rights into > the appropriate forests. > > If there's general agreement on this then I'll arrange for the warning > header on bugs.openjdk.java.net to be modified accordingly. > > - Mark > > > From ronald-freebsd8 at klop.yi.org Thu Mar 19 10:32:08 2009 From: ronald-freebsd8 at klop.yi.org (Ronald Klop) Date: Thu, 19 Mar 2009 18:32:08 +0100 Subject: freebsd supports openjdk 6 also Message-ID: Hello, Is it possible to add FreeBSD to this page? http://openjdk.java.net/install/ The procedure to install is this: su - cd /usr/ports/java/openjdk6 make install && make clean Thanks for all the hard work, Ronald. From Tim.Bell at Sun.COM Fri Mar 27 11:46:33 2009 From: Tim.Bell at Sun.COM (Tim Bell) Date: Fri, 27 Mar 2009 11:46:33 -0700 Subject: OpenJDK Community Code Review server rollout Message-ID: <49CD1F09.2040801@sun.com> Mark Wielaard mark at klomp.org wrote: > Would it be possible to tell the server to give the patches type > text/plain instead of application/octet-stream like > webrev.invokedynamic.info does? Done. My apology for the delay in making what turned out to be a trivial change. I added entries for file extensions that I could see people are using on cr.openjdk.java.net, and also set the final default to "text/plain". Please let me know if I missed anything. Tim Bell cr% gdiff lighttpd.conf.old lighttpd.conf 58d57 < 73a73 > ".jar" => "application/zip", 92a93 > ".ad" => "text/plain", 93a95,100 > ".d" => "text/plain", > ".sh" => "text/plain", > ".rc" => "text/plain", > ".bat" => "text/plain", > ".gmk" => "text/plain", > ".asm" => "text/plain", 94a102,110 > ".hpp" => "text/plain", > ".java" => "text/plain", > ".map" => "text/plain", > ".out" => "text/plain", > ".lst" => "text/plain", > ".list" => "text/plain", > ".patch" => "text/plain", > ".policy" => "text/plain", > ".make" => "text/plain", 100a117 > ".mf" => "text/xml", 111c128,129 < ".tar.bz2" => "application/x-bzip-compressed-tar" --- > ".tar.bz2" => "application/x-bzip-compressed-tar", > "" => "text/plain" 112a131,132 > # ^^^^ That last entry is to make the default mime type text/plain > # tbell Fri Mar 27 11:12:28 PDT 2009