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 AE395D39D for ; Thu, 5 Jul 2012 03:18:47 +0000 (UTC) Received: (qmail 25896 invoked by uid 500); 5 Jul 2012 03:18:46 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 25548 invoked by uid 500); 5 Jul 2012 03:18:44 -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 25477 invoked by uid 99); 5 Jul 2012 03:18:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 03:18:41 +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 (athena.apache.org: domain of phoenix.wanglf@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 03:18:34 +0000 Received: by obcva7 with SMTP id va7so12460758obc.6 for ; Wed, 04 Jul 2012 20:18:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=og2dX/sLSNKk5XnYjES/qHG1cPUm9BQsCZc92iKxoYA=; b=xfs0O/T0fClYqeXYu+qCWDp2CjSnufrcClLjTSJAgjRRJhKNssbTrqIzP4rO5mkGJZ iW6hm9nkuM33mf+0mI7qLTmDu/8a7kENReroUK1ORvsefOb+Y1yT1FjZlz2NceOenWiW 8e4/UDZM3WS6Oyn2J8r/42IF1dU0BlrcDOgjkxeiy6/Hjel7Yie/zxJH4CH8W+6Wt89Y TLQM1lutblszfRdVGA7kolT7IMx/kxRStONjQ55UMjjO9QD8feg36Hd48pbdij2cGVEE cgT7iCnGQPAh6KtLBwfkca6WePVgmbQsgv515iyRXfKg+JaGXdasMIKtKv1rb3ZvrGrz PywQ== MIME-Version: 1.0 Received: by 10.50.181.232 with SMTP id dz8mr13183971igc.72.1341458294052; Wed, 04 Jul 2012 20:18:14 -0700 (PDT) Received: by 10.64.24.167 with HTTP; Wed, 4 Jul 2012 20:18:13 -0700 (PDT) Date: Thu, 5 Jul 2012 11:18:13 +0800 Message-ID: Subject: [QA]When tester can close release blocker defect From: Li Feng Wang To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae934064b19186e04c40c99cf X-Virus-Checked: Checked by ClamAV on apache.org --14dae934064b19186e04c40c99cf Content-Type: text/plain; charset=ISO-8859-1 Hi, all, I am verifying some resolved 3.4.1 release blocker defects. Some fixed on trunk, some fixed on branch, some fixed on both trunk and branch I usually verify defects on stream, which fixed code exist, then close it. But I think tester can close defect, that must fixed on trunk. I want to confirm when tester close release blocker defect, Do we need to ensure the defect fixed on trunk? or Tester can close defect after verified defect on branch, then need verfiy all release blocker defects on trunk before release? -- Best Wishes, LiFeng Wang --14dae934064b19186e04c40c99cf--