Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 80632 invoked from network); 28 Dec 2006 12:58:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Dec 2006 12:58:36 -0000 Received: (qmail 57193 invoked by uid 500); 28 Dec 2006 12:58:36 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 57156 invoked by uid 500); 28 Dec 2006 12:58:36 -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 57137 invoked by uid 99); 28 Dec 2006 12:58:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2006 04:58:36 -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.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2006 04:58:26 -0800 Received: by ug-out-1314.google.com with SMTP id z36so3428022uge for ; Thu, 28 Dec 2006 04:57:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qS7kdNF9xwpd0GfG81D9jO9M9L7V+F6l48ilOZ0ThJ0Qv3q+rBcTDje1Edaz13tz3UJJ5B2EmKMxdBrcPetcvRs7XXitCGzpKgY8PQ/AgKlAwBs0w4KaLTwq3Rx8/1IjFrew2XSab+ci/9j7e7rEOvRXAFD1uUKXlZEbMixz6SM= Received: by 10.78.133.10 with SMTP id g10mr347969hud.1167310674237; Thu, 28 Dec 2006 04:57:54 -0800 (PST) Received: by 10.78.107.15 with HTTP; Thu, 28 Dec 2006 04:57:54 -0800 (PST) Message-ID: Date: Thu, 28 Dec 2006 15:57:54 +0300 From: "Alexey Petrenko" To: dev@harmony.apache.org Subject: Re: Re: How to mark ready-to-integrate JIRAs? In-Reply-To: <3D8E84095C6A524A985B787423094E4095D867@mssmsx411> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3D8E84095C6A524A985B787423094E4095D867@mssmsx411> X-Virus-Checked: Checked by ClamAV on apache.org 2006/12/28, Zakharov, Vasily M : > What I propose is a simple tag, like [fix_available] or such, > added to a JIRA comment. It's no more difficult than adding > the same tag to a mail subject. There is no such strong restrictions for dev list because I, for example, reads almost all dev messages. That's not true for commits list. SY, Alexey > -----Original Message----- > From: Alexey Petrenko [mailto:alexey.a.petrenko@gmail.com] > Sent: Thursday, December 28, 2006 3:39 PM > To: dev@harmony.apache.org > Subject: Re: Re: How to mark ready-to-integrate JIRAs? > > 2006/12/28, Zakharov, Vasily M : > > Adding a mark to a JIRA comment sends a mail to commits list, > > and may be easily filtered out of "ALL the JIRA traffic". > Right. > But in this case ALL the contributors should use exactly the same > phrase in comment. This could be not so easy. > > > > > And as these messages are only interesting to committers, > > I think it's more convenient to have them in commits list, > > not the dev-list. > > > > Also, that way you can search in JIRA database, in addition > > to mail. > > > > Vasily > > > > > > -----Original Message----- > > From: Alexey Petrenko [mailto:alexey.a.petrenko@gmail.com] > > Sent: Thursday, December 28, 2006 3:27 PM > > To: dev@harmony.apache.org > > Subject: Re: Re: How to mark ready-to-integrate JIRAs? > > > > 2006/12/28, Zakharov, Vasily M : > > > > > > > You can skip, comitters do not skip, you are happy. Unbelievable? > > > I have nothing against the [tag] idea, I just wonder how would it > > help. > > > What would be the difference of reading such marks and reading > > > harmony-commits list? :) > > It's easy... commits list receives ALL the JIRA traffic. But messages > > which needs additional community attention will be sent to dev. And > > number of such issues is much less then ALL. > > > > SY, Alexey > > > > > -----Original Message----- > > > From: news [mailto:news@sea.gmane.org] On Behalf Of Egor Pasko > > > Sent: Thursday, December 28, 2006 8:05 AM > > > To: dev@harmony.apache.org > > > Subject: Re: How to mark ready-to-integrate JIRAs? > > > > > > On the 0x24D day of Apache Harmony Vasily M. Zakharov wrote: > > > > > maybe we adopt a new [tag] for traffic? > > > > > > > > It seems to me, everybody would soon skip it without looking. > > > > > > You can skip, comitters do not skip, you are happy. Unbelievable? > > > > > > > And those few who wouldn't, read harmony-commits list anyway and > see > > > any > > > > changes occuring. > > > > > > > > It's better not to write a mail at all, than write it marking > "this > > is > > > > non-important message, > > > > don't read it" - the result is the same, but the traffic is higher > > and > > > > more time is spent. > > > > And we already have a list for such "non-important" messages, > > > > harmony-commits. > > > > > > > > Vasily > > > > > > > > > > > > -----Original Message----- > > > > From: Geir Magnusson Jr. [mailto:geir@pobox.com] > > > > Sent: Thursday, December 28, 2006 1:00 AM > > > > To: dev@harmony.apache.org > > > > Subject: Re: How to mark ready-to-integrate JIRAs? > > > > > > > > > > > > On Dec 27, 2006, at 4:14 PM, Zakharov, Vasily M wrote: > > > > > > > > > Hi, all, > > > > > > > > > > There're many issues in our JIRA that can be closed or > integrated > > > > > with no much effort. Issues with simple patches but with no > > > > > "patch available" flag set, "Won't Fix" issues, non-bug > > differences > > > > > are all good examples. > > > > > > > > > > And closing an issue (in a right way) is always good as it > allows > > > > > that issue to be forgotten and put off everybody's mind - one > > > problem > > > > > less to think of. > > > > > > > > > > But we have no effective instrument for a contributor to attract > > > > > a committer's attention to a particular small issue. > > > > > > > > The dev list? Please? > > > > > > > > > > > > > > For now the only way to do that is writing to the dev-list, > > > > > which is not very effective - we already have traffic high > enough. > > > > > Moreover, that information is only relevant to committers, who > are > > > > > minority (though very important) in the list - all other > > > contributors > > > > > would read such a message for nothing, wasting their time. > > > > > > > > Not true! There are lots of benefits to this kind of thing, such > as > > > > raising more public awareness about the issue, let people with > ideas > > > > review and comment, etc > > > > > > > > > > > > > > The other way used now to attract a committer's attention, is > > > setting > > > > > "Patch available" flag. But I can only set it on my own issues, > > > > > and setting it is probably not appopriate for "Won't Fix" > issues. > > > > > > > > > > Probably we could introduce some keyword, for example, > > > FIX_AVAILABLE, > > > > > that contributors could add to their comments to the respective > > > JIRAs > > > > > and committers could search for using conventional JIRA search? > > > > > > > > > > This way the committers' reaction to patches could be faster and > > > > > choosing the right issue to put efforts to would be more > > > well-founded > > > > > and information-based for committers. > > > > > > > > > > What do you think? > > > > > > > > I'm going to be a stick in the mud here - the best way to get > > > > people's attention should be dev list - maybe we adopt a new [tag] > > > > for traffic? > > > > > > > > geir > > > > > > > > > > > > > > Vasily Zakharov > > > > > Intel Enterprise Solutions Software Division > > > > > > > > > > -- > > > Egor Pasko > > > > > >