Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com
 designates 209.85.213.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=HQj36Id63H+z2S9ZFs+rQ1igGdQsawirS8Uuu9Dqckrh/oWqpdG0mIEBaDTRf5GjMK
         PHs39+y+7iYKfs8ZKZeMpv/ViiODysHlDa4pn5pNGCR4BFnpUWzFZdmPevJ+GZqI5pmC
         BoUkqML2VH0vDpcVU6QE9RESVTi2BcbBr86hc=
Message-ID: <4D06473E.8080105@gmail.com>
Date: Mon, 13 Dec 2010 16:18:06 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
 rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: Next milestones: 5.0M16 and 6.0M4
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>
In-Reply-To: <AANLkTimDH8_5_dUxCrOTWqMiRCx+Vy0MnSCrDDarGM74@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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
>>>>
>>>
>>>
>>>
>>
> 
> 
>