Path: g2news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!backlog2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 28 Mar 2009 16:02:31 -0500
Return-Path: <dba...@dbaron.org>
X-Original-To: governa...@lists.mozilla.org
Delivered-To: governa...@lists.mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Date: Sat, 28 Mar 2009 17:02:23 -0400
From: "L. David Baron" <dba...@dbaron.org>
To: governa...@lists.mozilla.org
Subject: Re: Moving patches from posted-to-bug to in-the-tree: a process
	discussion
References: <j-GdnQwM6bLY9VHUnZ2dnUVZ_q7inZ2d@mozilla.org>
	<r9CdnTg3M5ytSVHUnZ2dnUVZ_qWdnZ2d@mozilla.org>
	<A9226CCA-D53B-4F0D-A83C-8AE041F02260@mozilla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A9226CCA-D53B-4F0D-A83C-8AE041F02260@mozilla.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: governa...@lists.mozilla.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the governance and running of the Mozilla project
	<governance.lists.mozilla.org>
List-Unsubscribe: <https://lists.mozilla.org/options/governance>,
	<mailto:governance-requ...@lists.mozilla.org?subject=unsubscribe>
List-Post: <mailto:governa...@lists.mozilla.org>
List-Help: <mailto:governance-requ...@lists.mozilla.org?subject=help>
List-Subscribe: <https://lists.mozilla.org/listinfo/governance>,
	<mailto:governance-requ...@lists.mozilla.org?subject=subscribe>
Newsgroups: mozilla.governance
Message-ID: <mailman.1553.1238274151.13346.governance@lists.mozilla.org>
Lines: 30
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 63.245.208.166
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-Z78/yWOyTUTsWXGyh8omIRRqEWPL06+7ZISrAXsFbtky0U5tKvZJ6t3ThsKJhQNNpSLaDZ2QOGzTEig!adeBuI+83AsCFE6eFGQdDyjc7LkrLPZ8jrqYvS56QZGWmF24kZoICrMiHBOZrGfBe55ivzHZI9bq!0ptaCjGyUC5xbl61jfdByY2Ra/pgY05/
X-Complaints-To: abuse@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.39
X-Original-Bytes: 3728

On Friday 2009-03-27 10:59 -0400, Mike Beltzner wrote:
> I'm not sure that we need new or additional process here, to be honest. 
> It is the responsibility of a bug owner to ensure that it transitions 
> from state to state to state, and it's the responsibility of a component 
> owner to ensure that bugs are actively being triaged and moved through 
> the states and closed out if they're languishing or not getting 
> attention. My feeling is that the more process we have, the harder things 
> are to understand, and we have quite enough to understand already.

One thing that Jesse suggested a few weeks ago (in conversation at
lunch, I think) is that Bugzilla have a (queryable) notion of who is
expected to take the next action in a bug (and what that action is).
This way we could see queues of things other than review requests.

Another thought I had is that perhaps we could find tracking this
information easier if Bugzilla's "Status" field reflected the actual
statuses, e.g., by replacing "ASSIGNED" with "fix under
development", "waiting for review", and "waiting for checkin" with
an appropriately-defaulted checkbox to update this status as one
would expect when editing attachments.

(Personally, I track my patches-in-progress by having them all in a
single mercurial queue.  If it's not in that queue, I have no plans
to commit it.)

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/