Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E3237D891 for ; Thu, 21 Jun 2012 03:51:28 +0000 (UTC) Received: (qmail 56519 invoked by uid 500); 21 Jun 2012 03:51:28 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 56383 invoked by uid 500); 21 Jun 2012 03:51:28 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 56307 invoked by uid 99); 21 Jun 2012 03:51:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 03:51:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dennis.hamilton@acm.org designates 216.119.133.2 as permitted sender) Received: from [216.119.133.2] (HELO a2s42.a2hosting.com) (216.119.133.2) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 03:51:19 +0000 Received: from 71-217-73-181.tukw.qwest.net ([71.217.73.181]:32876 helo=Astraendo) by a2s42.a2hosting.com with esmtpa (Exim 4.77) (envelope-from ) id 1ShYQ6-002fwp-MP for ooo-dev@incubator.apache.org; Wed, 20 Jun 2012 23:50:58 -0400 Reply-To: From: "Dennis E. Hamilton" To: References: In-Reply-To: Subject: RE: [DISCUSS]What is the criteria for 3.4.1 release blocker? Date: Wed, 20 Jun 2012 20:51:02 -0700 Organization: NuovoDoc Message-ID: <001901cd4f61$14622210$3d266630$@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLrKnm+fDJ9Qnuj0XQk9SbatYtcwwF/gv4tAgMbBoaUrFdwIA== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s42.a2hosting.com X-AntiAbuse: Original Domain - incubator.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - acm.org X-Virus-Checked: Checked by ClamAV on apache.org I think safety is of high value. That includes security issues and also data loss/corruption. The last = includes crashers that result in unrecoverable loss of work. Hidden = loss of work and document corruption that does not appear until the = document is opened later is particularly serious. - Dennis -----Original Message----- From: dongjun zong [mailto:zongdj001@gmail.com]=20 Sent: Wednesday, June 20, 2012 20:31 To: ooo-dev@incubator.apache.org Subject: Re: [DISCUSS]What is the criteria for 3.4.1 release blocker? I think high severity regression issue, common usage function related = issue should be considered as release blocker. 2012/6/21 Ji Yan > From my point of view, security and high usability issue should be set = as > blocker > > 2012/6/21 debin lei > > > Hi, All > > I noticed that there are some issues, which are proposed as 3.4.1 = release > > blocker recently. However, I am not sure what is the criteria for = the > > release blocker? > > Is it regression or impact serious ? Or high benefit to risk ratio = from > dev > > view ? > > I think maybe consider more things, but not sure. > > So if you can give your criteria and discuss here to make the things = more > > clear will be very helpful. > > Thanks. > > > > Best regards. > > Lei De Bin > > > > > > -- > > > Thanks & Best Regards, Yan Ji >