Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44984 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90162 invoked from network); 16 Jul 2009 03:54:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jul 2009 03:54:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=philip@roshambo.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=philip@roshambo.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.198.225 cause and error) X-PHP-List-Original-Sender: philip@roshambo.org X-Host-Fingerprint: 209.85.198.225 rv-out-0506.google.com Received: from [209.85.198.225] ([209.85.198.225:4884] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F3/78-47962-584AE5A4 for ; Wed, 15 Jul 2009 23:54:46 -0400 Received: by rv-out-0506.google.com with SMTP id g37so1176527rvb.7 for ; Wed, 15 Jul 2009 20:54:43 -0700 (PDT) Received: by 10.140.203.18 with SMTP id a18mr4999068rvg.217.1247716483153; Wed, 15 Jul 2009 20:54:43 -0700 (PDT) Received: from ?192.168.1.2? (c-76-22-32-17.hsd1.wa.comcast.net [76.22.32.17]) by mx.google.com with ESMTPS id f21sm30008332rvb.56.2009.07.15.20.54.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 15 Jul 2009 20:54:41 -0700 (PDT) Cc: Sriram Natarajan , PHP internals Message-ID: <3AEF93D9-A92A-4CAA-9754-603423BA3B29@roshambo.org> To: jani.taskinen@iki.fi In-Reply-To: <4A5E245E.7080402@sci.fi> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Wed, 15 Jul 2009 20:54:42 -0700 References: <4A5E137E.3010905@Sun.COM> <4A5E245E.7080402@sci.fi> X-Mailer: Apple Mail (2.935.3) Subject: Re: [PHP-DEV] bug tracker planning From: philip@roshambo.org (Philip Olson) On Jul 15, 2009, at 11:47 AM, Jani Taskinen wrote: > Sriram Natarajan wrote: >> Hi >> bug tracking system also need the ability to mark a current bug as >> duplicate . Currently, all those bugs are marked as 'Bogus'. Also, >> it would be nice if we can have the ability to capture related bugs >> together. >> - Sriram > And we're not adding anymore statuses. Status is irrelevant for bug > being related to something or not. I think we should bring back the duplicate status for duplicate bugs, and include a bug number field to be submitted instead of sometimes writing a bug number as a comment that links if we remembered the syntax. And besides, the new Bugtracker already has the duplicate status much like its mother pearweb/bugs has. As for 'capturing related bugs', I imagine the [optional] tagging would help with that... or do you have something specific in mind? Regards, Philip