From ooo-dev-return-21924-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Tue Jun 26 16:14:50 2012 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 2890A9ED6 for ; Tue, 26 Jun 2012 16:14:50 +0000 (UTC) Received: (qmail 61518 invoked by uid 500); 26 Jun 2012 16:14:49 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 61444 invoked by uid 500); 26 Jun 2012 16:14:49 -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 61435 invoked by uid 99); 26 Jun 2012 16:14:49 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 16:14:49 +0000 Received: from localhost (HELO mail-vb0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 16:14:49 +0000 Received: by vbbfr13 with SMTP id fr13so58997vbb.6 for ; Tue, 26 Jun 2012 09:14:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.108.15 with SMTP id d15mr2691816vcp.37.1340727288475; Tue, 26 Jun 2012 09:14:48 -0700 (PDT) Received: by 10.220.190.13 with HTTP; Tue, 26 Jun 2012 09:14:48 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Jun 2012 12:14:48 -0400 Message-ID: Subject: Re: AOO testing status update as of 2012/06/26 From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jun 26, 2012 at 10:49 AM, Ji Yan wrote: > HI all, > > =C2=A0 After AOO 3.4 release, we, QE, volunteer didn't send out weekly re= port > to brief our activity, to make sure we are on the same page, I'll update > you with our main activity and achievement: > 1. Built up VCLAuto framework which has been deliver to trunk stream, > anyone with Java experience is able to write test script under this > framework. > 2. 252 defect opened by people from IBM Symphony team which the defect > doesn't exist in Symphony. > 3. Confirmed 174 UNCONFIRMED issues in bugzilla. > 4. Verified =C2=A0184 RESOLVED issues in bugzilla > 5. Work out AOO 3.4.1 test plan and put it on wiki page > 6. Start AOO 3.4.1 fixed defect verification > 7. AOO 3.4.1 general usage testing is ongoing. > > I'll keep you post with AOO 3.4.1 and AOO 3.5 testing status in next week= . > -- Good report. Thanks! Something to consider for next report. When we give our quarterly Board Report for the entire project, two of the questions are: -- How has the community developed since the last report -- How has the project developed since the last report. The work done by the Symphony QA team is excellent progress to report for "how has the project developed?". But is there anything the Symphony QA team can do to help develop the community as well? I think it would be great if we could brainstorm on ideas for encouraging and enabling other volunteers to help with the QA work. Not just existing project members, but also new volunteers we might recruit. -Rob > > > Thanks & Best Regards, Yan Ji