Return-Path: 
 <harmony-dev-return-19148-apmail-incubator-harmony-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org
Received: (qmail 32466 invoked from network); 16 Nov 2006 15:19:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 16 Nov 2006 15:19:24 -0000
Received: (qmail 57110 invoked by uid 500); 16 Nov 2006 15:19:31 -0000
Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org
Received: (qmail 57076 invoked by uid 500); 16 Nov 2006 15:19:30 -0000
Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:harmony-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:harmony-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:harmony-dev@incubator.apache.org>
List-Id: <harmony-dev.incubator.apache.org>
Reply-To: harmony-dev@incubator.apache.org
Delivered-To: mailing list harmony-dev@incubator.apache.org
Received: (qmail 57067 invoked by uid 99); 16 Nov 2006 15:19:30 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 07:19:30 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of gcjhd-harmony-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 07:19:16 -0800
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1Gkj0W-0001Pk-Oe
	for harmony-dev@incubator.apache.org; Thu, 16 Nov 2006 16:18:28 +0100
Received: from msfwpr01.ims.intel.com ([62.118.80.132])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <harmony-dev@incubator.apache.org>;
 Thu, 16 Nov 2006 16:18:28 +0100
Received: from egor.pasko by msfwpr01.ims.intel.com with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <harmony-dev@incubator.apache.org>;
 Thu, 16 Nov 2006 16:18:28 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: harmony-dev@incubator.apache.org
From: Egor Pasko <egor.pasko@gmail.com>
Subject: Re: [jira] Patch available setting
Date: 16 Nov 2006 21:19:11 +0600
Lines: 72
Message-ID: <u8xibwhao.fsf@gmail.com>
References: <fc2fc95c0611130930l1120647aia688c50c27dce8e3@mail.gmail.com>
 <455A612D.8060502@pobox.com> <uwt5xxolg.fsf@gmail.com>
 <455B9413.1000101@pobox.com> <uy7qbwkfj.fsf@gmail.com>
 <455C7B61.30205@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: msfwpr01.ims.intel.com
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org

On the 0x223 day of Apache Harmony Geir Magnusson, Jr. wrote:
> Egor Pasko wrote:
> > On the 0x223 day of Apache Harmony Geir Magnusson, Jr. wrote:
> >> Egor Pasko wrote:
> >>> On the 0x222 day of Apache Harmony Geir Magnusson, Jr. wrote:
> >>>> I thought we had it configured that when a JIRA is modified, the
> >>>> reporter is notified directly...  I'm not sure that really helps
> >>>> though. I wonder if we should just open things up a bit and let any
> >>>> user modify a JIRA and see what happens.
> >>> reporters are notified, that's right
> >>> But what if <reporter>=<patch publisher>? Then someone still needs to
> >>> review. Sometimes, reporters are not familiar with the components
> >>> fixed, someone needs to pick up a review in this case too.
> >> That's why I watch things I'm interested in.
> >>
> >>> I just look at all Harmony JIRA notifications. There are a lot, but
> >>> most can be safely skipped by subject.
> >> Right - do a watch on the JIRAs you are interested in - they come to
> >> you directly, not to the project JIRA stream.
> > Is there any other way to be notified with new issues than to
> > subscribe for the whole JIRA stream? I would love to use it.
> 
> I want to be sure to get the whole stream, and then just filter for
> things I want to look for.
> 
> Unless this is something that lots of people need - having a separate
> "new JIRA" mail stream, I think that you might want to try that :)

You knew that! I am like lots of people dying from a separate "new
JIRA" stream desire. Thanks for suggestion, I should heve found that,
pretty obvious.

Now back to fighting this killing-me-outlook that has a
limit-to-number-of-filters feature that I constantly suffer from.

> geir
> 
> > P.S: "watch" is a good feature, I have been using it.
> >
> >> geir
> >>
> >>>> geir
> >>>>
> >>>> Sian January wrote:
> >>>>> Hi,
> >>>>> I have just discovered that it's not possible for a contributor to
> >>>>> set
> >>>>> "Patch available" on a JIRA unless they reported it.  (I'm not sure about
> >>>>> committers as I'm not one...)  I imagine this is to stop people coming in
> >>>>> and editing other details on the JIRA, so I can see that it makes
> >>>>> sense.  My
> >>>>> question is, what is the best thing to do if I attach a patch to a JIRA and
> >>>>> I can't set "Patch available"?  I can think of three alternatives at the
> >>>>> moment:
> >>>>> 1. Assume that the reporter will notice and set it themselves (or
> >>>>> commit the
> >>>>> fix if they're also a comitter)
> >>>>> 2. E-mail the reporter privately
> >>>>> 3. Post to the mailing list
> >>>>> Or a fourth alternative would be a combination of the above where
> >>>>> the person
> >>>>> who contributed the patch waits a few days before doing either 2 or 3.  Any
> >>>>> thoughts on what would be best?
> >>>>> Thanks,
> >>>>> Sian
> >>>>>
> >>>>
> >
> 

-- 
Egor Pasko