Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (nike.apache.org: domain of clraychen@gmail.com designates
 209.85.214.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=JQRrGOrVkcxSz9m9U/Dj17dzVL2UqUM2PypQGKYt2ORdZzccDn1mDuxYcufpN9zxzU
         uMIX6z4rOMrRYPpKh5RuEYtdV5UEKTv/w9BH5I5s67quTypi+x4ed/t4/TutaV4bmnU+
         7GwD7YM9pKeM0L+dAiBYG2/dckpdJKkcngRmg=
MIME-Version: 1.0
In-Reply-To: <4D06473E.8080105@gmail.com>
References: <201011091818.oA9IIkgm002702@d12av03.megacenter.de.ibm.com>
	<AANLkTim8D0g8yCCfdXyKn46DTj+euYwBge6mVc2tAdqH@mail.gmail.com>
	<4D06056B.7080103@gmail.com>
	<AANLkTimq_XVVQ3pcpOWD0jQ0-QGb7A2t2C-ft7TCqhoo@mail.gmail.com>
	<4D063FB2.9020408@gmail.com>
	<AANLkTimDH8_5_dUxCrOTWqMiRCx+Vy0MnSCrDDarGM74@mail.gmail.com>
	<4D06473E.8080105@gmail.com>
Date: Sat, 18 Dec 2010 00:58:51 +0800
Message-ID: <AANLkTi=Uz6Q-TXN8Rk_msOxSHi=kcby0FyWHL6niTGo3@mail.gmail.com>
Subject: Re: Next milestones: 5.0M16 and 6.0M4
From: Ray Chen <clraychen@gmail.com>
To: dev@harmony.apache.org
Content-Type: multipart/alternative; boundary=0022152d7c5fbba34404979e15e3

--0022152d7c5fbba34404979e15e3
Content-Type: text/plain; charset=ISO-8859-1

Hi Tim,
Sorry, I am very busy these days.
Currently, we still have some JDWP test failures.
Do they stop us to publish a new level?

If no, what process, we should follow?

Thanks!

On Tue, Dec 14, 2010 at 12:18 AM, Tim Ellison <t.p.ellison@gmail.com> wrote:

> On 13/Dec/2010 15:49, Ray Chen wrote:
> > Hmmm... OK, let's deferring that to the next milestone.
>
> If it wasn't fixed before the code freeze, then there needs to be a good
> reason why it is being fixed during the testing and publication period.
>  It's the only way we can get stability during testing -- otherwise the
> code is changing and we never converge on a milestone.
>
> If you think this needs to be fixed, just say why, otherwise we'll move
> the target out to a later date.
>
> Regards,
> Tim
>
>
> > On Mon, Dec 13, 2010 at 11:45 PM, Tim Ellison <t.p.ellison@gmail.com>
> wrote:
> >
> >> On 13/Dec/2010 15:40, Ray Chen wrote:
> >>> FYI.
> >>> This defect should be fixed in this milestone, see
> >>> http://s.apache.org/harmony/roadmap mentioned by Mark
> >>
> >> I see it is targeted to this milestone, I'm questioning whether that is
> >> correct.
> >>
> >> Why do you think it needs to be fixed now rather than deferring to the
> >> next milestone?
> >>
> >> Regards,
> >> Tim
> >>
> >>
> >>> On Mon, Dec 13, 2010 at 7:37 PM, Tim Ellison <t.p.ellison@gmail.com>
> >> wrote:
> >>>
> >>>> On 13/Dec/2010 08:23, Ray Chen wrote:
> >>>>> Hi Comitters,
> >>>>> I have reviewed https://issues.apache.org/jira/browse/HARMONY-6656,
> >>>> seems
> >>>>> look good.
> >>>>> I remember that there should be at least two committers to agree to
> >> apply
> >>>> a
> >>>>> patch during code freeze time, right?
> >>>>>
> >>>>> Does anyone else can help to review this patch?
> >>>>
> >>>> During freeze time we only apply patches that are resolving blocking
> >>>> issues for the release to ensure we retain stability.
> >>>>
> >>>> Is this a regression from behavior that worked in the 5.0M15
> milestone?
> >>>> (I don't think so) or is it a major failure that means we should
> restart
> >>>> testing?
> >>>>
> >>>> I suggest this may be a candidate for defering until the next
> milestone.
> >>>>
> >>>> Regards,
> >>>> Tim
> >>>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
>


-- 
Regards,

Ray Chen

--0022152d7c5fbba34404979e15e3--