Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of gcjhd-harmony-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@harmony.apache.org
From: Egor Pasko <egor.pasko@gmail.com>
Subject: Re: How to mark ready-to-integrate JIRAs?
Date: 28 Dec 2006 10:55:00 +0600
Lines: 54
Message-ID: <uhcvgvcuz.fsf@gmail.com>
References: <3D8E84095C6A524A985B787423094E4095D6D9@mssmsx411>
 <A4F58316-DEA5-420F-A6BF-4045AE73D1DE@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Sender: news <news@sea.gmane.org>

On the 0x24D day of Apache Harmony Geir Magnusson, Jr. wrote:
> 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?

Good idea.
([fix-available] or [fix]) and [wontfix]

-- 
Egor Pasko