Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 51777 invoked from network); 12 Feb 2007 12:55:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2007 12:55:43 -0000 Received: (qmail 42861 invoked by uid 500); 12 Feb 2007 12:55:47 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 42830 invoked by uid 500); 12 Feb 2007 12:55:47 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 42821 invoked by uid 99); 12 Feb 2007 12:55:47 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2007 04:55:47 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of alexey.a.petrenko@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2007 04:55:37 -0800 Received: by ug-out-1314.google.com with SMTP id z36so1204640uge for ; Mon, 12 Feb 2007 04:55:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jQBQZifd6/rA4qFGbrlO0PjqXpmXMiFDbQQXnzFPmxfWYf9ZGUzN048/PTDkvN8Nw9TYW4fn2foexLMATfu6JV4iDz3OfLPGb2bhCnw95XjgdEP450RI2G9jMjHVvpng00YoUeiK9In1BZux6kLtXa/OFWy+KR2aHu0S7kJuPuI= Received: by 10.114.208.8 with SMTP id f8mr5686802wag.1171284915369; Mon, 12 Feb 2007 04:55:15 -0800 (PST) Received: by 10.114.123.16 with HTTP; Mon, 12 Feb 2007 04:55:10 -0800 (PST) Message-ID: Date: Mon, 12 Feb 2007 15:55:10 +0300 From: "Alexey Petrenko" To: dev@harmony.apache.org Subject: Re: [general] When to bring a conversation out of JIRA... In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org I agree that we need to bring out of the JIRA all the long or not-obvious conversations. And then add a link to this conversation to original JIRA issue. SY, Alexey 2007/2/11, Geir Magnusson Jr. : > So over the last few days, I've been working off and on trying to > debug some classloader stuff using eclipse. it's been a hoot, since > I don't know eclipse very well. > > When working w/ DRLVM as the runtime JRE for running and debugging > unit tests, I ran into a few problems with what appeared to be > related to JDPA et al. Gregory pointed me to http:// > issues.apache.org/jira/browse/HARMONY-3047, a JIRA on what appeared > to be related issues. > > Now, reading through, I saw at least one thing (having to put the > jdwp shared lib and the transport share lib) that I spent a bit of > time figuring out myself. Reading down the thread, there seemed to be > other interesting things in there. > > Now, I'm an advocate of having tech conversations out on the mailing > list, rather than in JIRA, because I believe it's better for a whole > bunch of reasons. I also understand how it's appropriate for some > comments to remain on JIRA if they tend to be narrow and specific. > > Should we try to suggest/mandate a practice that when a JIRA comment > thread gets "long", that we make an effort to bring it out? At least > consciously evaluate if there is going to be broader interest (in > this case) or broader experience that could help? > > I think we're missing some good opportunities to leverage the > collective abilities of the community as well as expose information > more broadly if we don't examine and address this. > > geir >