Return-Path: 
 <harmony-dev-return-18959-apmail-incubator-harmony-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org
Received: (qmail 29913 invoked from network); 15 Nov 2006 07:55:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Nov 2006 07:55:43 -0000
Received: (qmail 87180 invoked by uid 500); 15 Nov 2006 07:55:50 -0000
Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org
Received: (qmail 87149 invoked by uid 500); 15 Nov 2006 07:55:50 -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 87140 invoked by uid 99); 15 Nov 2006 07:55:50 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Nov 2006 23:55:50 -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 64.233.182.188 as permitted sender)
Received: from [64.233.182.188] (HELO nf-out-0910.google.com) (64.233.182.188)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Nov 2006 23:55:37 -0800
Received: by nf-out-0910.google.com with SMTP id p46so606957nfa
        for <harmony-dev@incubator.apache.org>;
 Tue, 14 Nov 2006 23:55:16 -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=omxZcvzFt2TA0bi5/OogFIIM2OKqxFqQrY/f+Q5LLkymk558EJ7+5aB2aJ7dpPE/gm8I9Qxed0o4QH1opsKVLzS70NLK4C37VlHnpixWMBZVAPoRcIiXeJhzuOv+15tF31BRwM6l+s8wgr32HBy2sj1y9AXFIOw/803E6zzZBw4=
Received: by 10.78.57.11 with SMTP id f11mr2029778hua.1163577315858;
        Tue, 14 Nov 2006 23:55:15 -0800 (PST)
Received: by 10.78.107.10 with HTTP; Tue, 14 Nov 2006 23:55:15 -0800 (PST)
Message-ID: <c3755b3a0611142355y6fa03d06k25324e5cb936fe5f@mail.gmail.com>
Date: Wed, 15 Nov 2006 10:55:15 +0300
From: "Alexey Petrenko" <alexey.a.petrenko@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Patch available setting
In-Reply-To: <uwt5xxolg.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fc2fc95c0611130930l1120647aia688c50c27dce8e3@mail.gmail.com>
	 <455A612D.8060502@pobox.com> <uwt5xxolg.fsf@gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

15 Nov 2006 11:31:39 +0600, Egor Pasko <egor.pasko@gmail.com>:
> 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.
The patch will be reviewed by committer at least.

> Sometimes, reporters are not familiar with the components
> fixed, someone needs to pick up a review in this case too.
>
> I just look at all Harmony JIRA notifications. There are a lot, but
> most can be safely skipped by subject.
That's good approach too.
Thanks for doing this!

SY, Alexey

> > 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
>
>