Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jogischmidt@googlemail.com
 designates 209.85.214.47 as permitted sender)
Date: Thu, 5 Jul 2012 08:05:36 +0200
From: "=?utf-8?Q?J=C3=BCrgen_Schmidt?=" <jogischmidt@googlemail.com>
To: ooo-dev@incubator.apache.org
Message-ID: <130B2C51DFC544E79C8FB185F808CF31@googlmail.com>
In-Reply-To: 
 <CAJ+c7QzuroMuZfOnjwpaEU=rRG6HRxquX8_Rj=h-sgL6a6ny9w@mail.gmail.com>
References: 
 <CABfS=dyGuK_Vc=mhuqVLCSFfTUtwcOhd+vrQUs-jWJ1xjkCtrg@mail.gmail.com>
 <CAJ+c7QzuroMuZfOnjwpaEU=rRG6HRxquX8_Rj=h-sgL6a6ny9w@mail.gmail.com>
Subject: Re: [QA]When tester can close release blocker defect
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4ff52eb0_3006c83e_67f8"

--4ff52eb0_3006c83e_67f8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Am Donnerstag, 5. Juli 2012 um 07:16 schrieb Ji Yan:
> Technically, I think the release blocker defects should also be integrated
> to trunk stream except for those branch stream special issue, such as
> 119978. So as QA we should ensure the defect is fixed in both branch and
> trunk stream.
> 
> 

exactly and we had already some discussion how to manage the workflow.
It seems that the majority prefer fixing an issue on trunk first and merge it in the branch on demand if it is a blocker issue.
I would suggest that we add the revision number for both trunk and branch as comments in the issue. That will help us to track it easier. 

Or does anybody have a better idea?

But I think it is the responsibility of the developer to fix it in both trees. Fix in trunk and merge in branch.

Juergen
> 
> 2012/7/5 Li Feng Wang <phoenix.wanglf@gmail.com>
> 
> > 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
> > 
> 
> 
> 
> 
> -- 
> 
> 
> Thanks & Best Regards, Yan Ji 


--4ff52eb0_3006c83e_67f8--