Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2CECCD069 for ; Mon, 5 Nov 2012 03:12:01 +0000 (UTC) Received: (qmail 57136 invoked by uid 500); 5 Nov 2012 03:12:00 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 56561 invoked by uid 500); 5 Nov 2012 03:11:59 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 55432 invoked by uid 500); 5 Nov 2012 03:11:57 -0000 Delivered-To: apmail-incubator-ooo-dev@incubator.apache.org Received: (qmail 55215 invoked by uid 99); 5 Nov 2012 03:11:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2012 03:11:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yanji.yj@gmail.com designates 209.85.223.175 as permitted sender) Received: from [209.85.223.175] (HELO mail-ie0-f175.google.com) (209.85.223.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2012 03:11:49 +0000 Received: by mail-ie0-f175.google.com with SMTP id c13so7468047ieb.6 for ; Sun, 04 Nov 2012 19:11:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=uUniU/p692VW30juoSlI8sy5QZlA/puc1vEVx+BEq3o=; b=OZ0c2X5v6a4meVohQ2DC9eXR/5QblgPAKSaGv8YFHrwtHIgPYwYLhlaWyXKX40slfE iJzNYYKVkCsG/+XA/lVeqZjzU9RRdI+MbB0A8edqP/3EqAHhPb8gxvHNrUwcjbx12NbG anCdSUxcA+3RvOgIkqchBtB+X7byJbarP7sC7WDZus7A9Iur3/kfdLMb+9gx436GBv3N KiPacYeoq4WLPMKqdpZ7e8iyOvyqMfWgIzPZrbW5oOerHePUAxNSUS2dLQMeyX730RdM k9NW/2Kfd9TKqu77aVlboWNcatAGUa8JckE4v6tfxui0NY5X3pocBfj4TloGwUwp/ZPF IuEA== MIME-Version: 1.0 Received: by 10.50.213.34 with SMTP id np2mr8125719igc.57.1352085088912; Sun, 04 Nov 2012 19:11:28 -0800 (PST) Received: by 10.64.59.103 with HTTP; Sun, 4 Nov 2012 19:11:28 -0800 (PST) In-Reply-To: <5093AE0C.20904@apache.org> References: <5093AE0C.20904@apache.org> Date: Mon, 5 Nov 2012 11:11:28 +0800 Message-ID: Subject: Re: [BZ]How does vote function work From: Ji Yan To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec5554fd26e43fc04cdb6d7e1 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5554fd26e43fc04cdb6d7e1 Content-Type: text/plain; charset=ISO-8859-1 I'm thinking about what's kind of defect triage criteria we should have. IMHO, in each milestone, we should have backlog defects fix plan. To give this defect list, what's criteria should be? High severity, high usability impact defects of course should be in that list, in the meanwhile, can we also add some defects which have more votes? 2012/11/2 Andrea Pescetti > Ji Yan wrote: > >> I'm curious how the vote function works in Bugzilla. Will we prioritize >> defect fix plan based on votes number? >> > > Not only on that, but votes are an indicator. When one has to pick > priorities, having dozens of votes for one issue can make a difference. > > Regards, > Andrea. > -- Thanks & Best Regards, Yan Ji --bcaec5554fd26e43fc04cdb6d7e1--