You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tim Ellison <t....@gmail.com> on 2009/05/15 17:42:55 UTC
[general] Milestone 10 countdown - 2 weeks
Just a reminder. We are entering feature freeze now, and there is just
one week left to go to our code freeze date.
No major new functionality gets dropped in from now until after M10.
Point bug fixes are still ok, and if you have time to do some testing
and fixing ahead of the test phase all the better.
Feature freeze Fri 15th May
Code freeze Fri 22nd May
Publish Fri 29th May
With the 'customary' definitions of what they mean.
Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
package listed in the Versions column to see those targeted for M10.
[1] http://issues.apache.org/jira/browse/HARMONY
Regards,
Tim
Re: [general] Milestone 10 - Code Freeze
Posted by Nathan Beyer <nd...@apache.org>.
I applied the change at r778555. If any issues pop-up, we can roll it back.
On Mon, May 25, 2009 at 8:44 PM, Sean Qiu <se...@gmail.com> wrote:
> +1
>
> I've taken a look at it as well. It is really important to us.
>
> Best Regards
> Sean, Xiao Xia Qiu
>
>
>
>
> 2009/5/26 Nathan Beyer <nd...@apache.org>:
>> I'd like to apply the patches for this issue
>> -https://issues.apache.org/jira/browse/HARMONY-6212
>> [classlib][luni] StringBuilder behavior affects the string got by the toString
>>
>> I've applied the test and fix locally and it seems good to me. This is
>> a pretty significant issue - String isn't immutable.
>>
>> Any other committers that can approve it?
>>
>> On Fri, May 22, 2009 at 5:31 AM, Oliver Deakin
>> <ol...@googlemail.com> wrote:
>>> And a follow up reminder - we are now in code freeze and testing period,
>>> aiming to publish M10 on Friday 29th May.
>>>
>>> As usual, defining a bug as "must-fix" in this milestone requires (at least)
>>> two committers agreement. Please raise test failures on the list and open
>>> JIRAs where appropriate.
>>>
>>> Regards,
>>> Oliver
>>>
>>> Tim Ellison wrote:
>>>>
>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>> one week left to go to our code freeze date.
>>>>
>>>> No major new functionality gets dropped in from now until after M10.
>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>> and fixing ahead of the test phase all the better.
>>>>
>>>> Feature freeze Fri 15th May
>>>> Code freeze Fri 22nd May
>>>> Publish Fri 29th May
>>>>
>>>> With the 'customary' definitions of what they mean.
>>>>
>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>> package listed in the Versions column to see those targeted for M10.
>>>>
>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>>
>>>>
>>>
>>> --
>>> Oliver Deakin
>>> Unless stated otherwise above:
>>> IBM United Kingdom Limited - Registered in England and Wales with number
>>> 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
>>> PO6 3AU
>>>
>>>
>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Sean Qiu <se...@gmail.com>.
+1
I've taken a look at it as well. It is really important to us.
Best Regards
Sean, Xiao Xia Qiu
2009/5/26 Nathan Beyer <nd...@apache.org>:
> I'd like to apply the patches for this issue
> -https://issues.apache.org/jira/browse/HARMONY-6212
> [classlib][luni] StringBuilder behavior affects the string got by the toString
>
> I've applied the test and fix locally and it seems good to me. This is
> a pretty significant issue - String isn't immutable.
>
> Any other committers that can approve it?
>
> On Fri, May 22, 2009 at 5:31 AM, Oliver Deakin
> <ol...@googlemail.com> wrote:
>> And a follow up reminder - we are now in code freeze and testing period,
>> aiming to publish M10 on Friday 29th May.
>>
>> As usual, defining a bug as "must-fix" in this milestone requires (at least)
>> two committers agreement. Please raise test failures on the list and open
>> JIRAs where appropriate.
>>
>> Regards,
>> Oliver
>>
>> Tim Ellison wrote:
>>>
>>> Just a reminder. We are entering feature freeze now, and there is just
>>> one week left to go to our code freeze date.
>>>
>>> No major new functionality gets dropped in from now until after M10.
>>> Point bug fixes are still ok, and if you have time to do some testing
>>> and fixing ahead of the test phase all the better.
>>>
>>> Feature freeze Fri 15th May
>>> Code freeze Fri 22nd May
>>> Publish Fri 29th May
>>>
>>> With the 'customary' definitions of what they mean.
>>>
>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>> package listed in the Versions column to see those targeted for M10.
>>>
>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>
>>> Regards,
>>> Tim
>>>
>>>
>>>
>>
>> --
>> Oliver Deakin
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
>> PO6 3AU
>>
>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Nathan Beyer <nd...@apache.org>.
I'd like to apply the patches for this issue
-https://issues.apache.org/jira/browse/HARMONY-6212
[classlib][luni] StringBuilder behavior affects the string got by the toString
I've applied the test and fix locally and it seems good to me. This is
a pretty significant issue - String isn't immutable.
Any other committers that can approve it?
On Fri, May 22, 2009 at 5:31 AM, Oliver Deakin
<ol...@googlemail.com> wrote:
> And a follow up reminder - we are now in code freeze and testing period,
> aiming to publish M10 on Friday 29th May.
>
> As usual, defining a bug as "must-fix" in this milestone requires (at least)
> two committers agreement. Please raise test failures on the list and open
> JIRAs where appropriate.
>
> Regards,
> Oliver
>
> Tim Ellison wrote:
>>
>> Just a reminder. We are entering feature freeze now, and there is just
>> one week left to go to our code freeze date.
>>
>> No major new functionality gets dropped in from now until after M10.
>> Point bug fixes are still ok, and if you have time to do some testing
>> and fixing ahead of the test phase all the better.
>>
>> Feature freeze Fri 15th May
>> Code freeze Fri 22nd May
>> Publish Fri 29th May
>>
>> With the 'customary' definitions of what they mean.
>>
>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>> package listed in the Versions column to see those targeted for M10.
>>
>> [1] http://issues.apache.org/jira/browse/HARMONY
>>
>> Regards,
>> Tim
>>
>>
>>
>
> --
> Oliver Deakin
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
> PO6 3AU
>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Tim Ellison <t....@gmail.com>.
Sian January wrote:
> End of the day sounds fine to me - I think that's what we've done before.
:-) I wasn't trying to be sneaky. If somebody else would take a look
and agree that the patch looks safe then I think we should include it
before we start the more thorough testing. If people think it is too
risky it can wait.
Tim
> 2009/5/22 Tim Ellison <t....@gmail.com>:
>> Oliver Deakin wrote:
>>> And a follow up reminder - we are now in code freeze and testing period,
>>> aiming to publish M10 on Friday 29th May.
>>>
>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>> least) two committers agreement. Please raise test failures on the list
>>> and open JIRAs where appropriate.
>> What time does the code freeze start today ;-) ?
>>
>> I'd like to propose that HARMONY-6074 patch is applied since it is
>> blocking Maven. The patch looks fine to me.
>>
>> Regards,
>> Tim
>>
>>
>>> Tim Ellison wrote:
>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>> one week left to go to our code freeze date.
>>>>
>>>> No major new functionality gets dropped in from now until after M10.
>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>> and fixing ahead of the test phase all the better.
>>>>
>>>> Feature freeze Fri 15th May
>>>> Code freeze Fri 22nd May
>>>> Publish Fri 29th May
>>>>
>>>> With the 'customary' definitions of what they mean.
>>>>
>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>> package listed in the Versions column to see those targeted for M10.
>>>>
>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>>
>>>>
>
>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Oliver Deakin <ol...@googlemail.com>.
Maybe I was a little specific with my timing ;) I think "end of the day"
is probably enough to give everyone a rough idea of when they can and
can't commit. As you say, it is probably worth mentioning this in future
milestone freezes.
Regards,
Oliver
Sian January wrote:
> Looks fine to me too, though it would be nice to also add a regression
> test at some point.
>
> It might be worth specifying freeze times in advance in the future (or
> it might just be overkill for the size of project that we are :-)).
>
>
>
> 2009/5/22 Oliver Deakin <ol...@googlemail.com>:
>
>> Yep, I'm happy with it being the end of the (working) day as well since the
>> feature freeze started around 5pm BST last friday. It would be nice to have
>> Maven working on M10 and the patch looks good to me. I have run the luni
>> tests with the patch applied and I see no new failures.
>>
>> Regards,
>> Oliver
>>
>> Sian January wrote:
>>
>>> End of the day sounds fine to me - I think that's what we've done before.
>>>
>>> 2009/5/22 Tim Ellison <t....@gmail.com>:
>>>
>>>
>>>> Oliver Deakin wrote:
>>>>
>>>>
>>>>> And a follow up reminder - we are now in code freeze and testing period,
>>>>> aiming to publish M10 on Friday 29th May.
>>>>>
>>>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>>>> least) two committers agreement. Please raise test failures on the list
>>>>> and open JIRAs where appropriate.
>>>>>
>>>>>
>>>> What time does the code freeze start today ;-) ?
>>>>
>>>> I'd like to propose that HARMONY-6074 patch is applied since it is
>>>> blocking Maven. The patch looks fine to me.
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>>
>>>>
>>>>
>>>>> Tim Ellison wrote:
>>>>>
>>>>>
>>>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>>>> one week left to go to our code freeze date.
>>>>>>
>>>>>> No major new functionality gets dropped in from now until after M10.
>>>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>>>> and fixing ahead of the test phase all the better.
>>>>>>
>>>>>> Feature freeze Fri 15th May
>>>>>> Code freeze Fri 22nd May
>>>>>> Publish Fri 29th May
>>>>>>
>>>>>> With the 'customary' definitions of what they mean.
>>>>>>
>>>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>>>> package listed in the Versions column to see those targeted for M10.
>>>>>>
>>>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>>>
>>>>>> Regards,
>>>>>> Tim
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>>
>> --
>> Oliver Deakin
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
>> PO6 3AU
>>
>>
>>
>
>
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Milestone 10 - Code Freeze
Posted by Sian January <si...@googlemail.com>.
Looks fine to me too, though it would be nice to also add a regression
test at some point.
It might be worth specifying freeze times in advance in the future (or
it might just be overkill for the size of project that we are :-)).
2009/5/22 Oliver Deakin <ol...@googlemail.com>:
> Yep, I'm happy with it being the end of the (working) day as well since the
> feature freeze started around 5pm BST last friday. It would be nice to have
> Maven working on M10 and the patch looks good to me. I have run the luni
> tests with the patch applied and I see no new failures.
>
> Regards,
> Oliver
>
> Sian January wrote:
>>
>> End of the day sounds fine to me - I think that's what we've done before.
>>
>> 2009/5/22 Tim Ellison <t....@gmail.com>:
>>
>>>
>>> Oliver Deakin wrote:
>>>
>>>>
>>>> And a follow up reminder - we are now in code freeze and testing period,
>>>> aiming to publish M10 on Friday 29th May.
>>>>
>>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>>> least) two committers agreement. Please raise test failures on the list
>>>> and open JIRAs where appropriate.
>>>>
>>>
>>> What time does the code freeze start today ;-) ?
>>>
>>> I'd like to propose that HARMONY-6074 patch is applied since it is
>>> blocking Maven. The patch looks fine to me.
>>>
>>> Regards,
>>> Tim
>>>
>>>
>>>
>>>>
>>>> Tim Ellison wrote:
>>>>
>>>>>
>>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>>> one week left to go to our code freeze date.
>>>>>
>>>>> No major new functionality gets dropped in from now until after M10.
>>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>>> and fixing ahead of the test phase all the better.
>>>>>
>>>>> Feature freeze Fri 15th May
>>>>> Code freeze Fri 22nd May
>>>>> Publish Fri 29th May
>>>>>
>>>>> With the 'customary' definitions of what they mean.
>>>>>
>>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>>> package listed in the Versions column to see those targeted for M10.
>>>>>
>>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>>
>>>>> Regards,
>>>>> Tim
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>
>>
>>
>
> --
> Oliver Deakin
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
> PO6 3AU
>
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Milestone 10 - Code Freeze
Posted by Oliver Deakin <ol...@googlemail.com>.
Yep, I'm happy with it being the end of the (working) day as well since
the feature freeze started around 5pm BST last friday. It would be nice
to have Maven working on M10 and the patch looks good to me. I have run
the luni tests with the patch applied and I see no new failures.
Regards,
Oliver
Sian January wrote:
> End of the day sounds fine to me - I think that's what we've done before.
>
> 2009/5/22 Tim Ellison <t....@gmail.com>:
>
>> Oliver Deakin wrote:
>>
>>> And a follow up reminder - we are now in code freeze and testing period,
>>> aiming to publish M10 on Friday 29th May.
>>>
>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>> least) two committers agreement. Please raise test failures on the list
>>> and open JIRAs where appropriate.
>>>
>> What time does the code freeze start today ;-) ?
>>
>> I'd like to propose that HARMONY-6074 patch is applied since it is
>> blocking Maven. The patch looks fine to me.
>>
>> Regards,
>> Tim
>>
>>
>>
>>> Tim Ellison wrote:
>>>
>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>> one week left to go to our code freeze date.
>>>>
>>>> No major new functionality gets dropped in from now until after M10.
>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>> and fixing ahead of the test phase all the better.
>>>>
>>>> Feature freeze Fri 15th May
>>>> Code freeze Fri 22nd May
>>>> Publish Fri 29th May
>>>>
>>>> With the 'customary' definitions of what they mean.
>>>>
>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>> package listed in the Versions column to see those targeted for M10.
>>>>
>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>>
>>>>
>>>>
>
>
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Milestone 10 - Code Freeze
Posted by Sian January <si...@googlemail.com>.
End of the day sounds fine to me - I think that's what we've done before.
2009/5/22 Tim Ellison <t....@gmail.com>:
> Oliver Deakin wrote:
>> And a follow up reminder - we are now in code freeze and testing period,
>> aiming to publish M10 on Friday 29th May.
>>
>> As usual, defining a bug as "must-fix" in this milestone requires (at
>> least) two committers agreement. Please raise test failures on the list
>> and open JIRAs where appropriate.
>
> What time does the code freeze start today ;-) ?
>
> I'd like to propose that HARMONY-6074 patch is applied since it is
> blocking Maven. The patch looks fine to me.
>
> Regards,
> Tim
>
>
>> Tim Ellison wrote:
>>> Just a reminder. We are entering feature freeze now, and there is just
>>> one week left to go to our code freeze date.
>>>
>>> No major new functionality gets dropped in from now until after M10.
>>> Point bug fixes are still ok, and if you have time to do some testing
>>> and fixing ahead of the test phase all the better.
>>>
>>> Feature freeze Fri 15th May
>>> Code freeze Fri 22nd May
>>> Publish Fri 29th May
>>>
>>> With the 'customary' definitions of what they mean.
>>>
>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>> package listed in the Versions column to see those targeted for M10.
>>>
>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>
>>> Regards,
>>> Tim
>>>
>>>
>>>
>>
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Milestone 10 - Code Freeze
Posted by Sean Qiu <se...@gmail.com>.
I've added a test case for this patch to avoid future regression.
Best Regards
Sean, Xiao Xia Qiu
2009/5/22 Tim Ellison <t....@gmail.com>:
> Looks like you have some code in the JIRA that can be trivially turned
> into a test case too.
>
> I say go ahead and commit it Sean.
>
> Regards,
> Tim
>
> Sean Qiu wrote:
>> Yeap, user is important to us. lol
>>
>> Thanks for reviewing.
>>
>> Best Regards
>> Sean, Xiao Xia Qiu
>>
>>
>>
>>
>> 2009/5/22 Tim Ellison <t....@gmail.com>:
>>> Oliver Deakin wrote:
>>>> And a follow up reminder - we are now in code freeze and testing period,
>>>> aiming to publish M10 on Friday 29th May.
>>>>
>>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>>> least) two committers agreement. Please raise test failures on the list
>>>> and open JIRAs where appropriate.
>>> What time does the code freeze start today ;-) ?
>>>
>>> I'd like to propose that HARMONY-6074 patch is applied since it is
>>> blocking Maven. The patch looks fine to me.
>>>
>>> Regards,
>>> Tim
>>>
>>>
>>>> Tim Ellison wrote:
>>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>>> one week left to go to our code freeze date.
>>>>>
>>>>> No major new functionality gets dropped in from now until after M10.
>>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>>> and fixing ahead of the test phase all the better.
>>>>>
>>>>> Feature freeze Fri 15th May
>>>>> Code freeze Fri 22nd May
>>>>> Publish Fri 29th May
>>>>>
>>>>> With the 'customary' definitions of what they mean.
>>>>>
>>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>>> package listed in the Versions column to see those targeted for M10.
>>>>>
>>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>>
>>>>> Regards,
>>>>> Tim
>>>>>
>>>>>
>>>>>
>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Tim Ellison <t....@gmail.com>.
Looks like you have some code in the JIRA that can be trivially turned
into a test case too.
I say go ahead and commit it Sean.
Regards,
Tim
Sean Qiu wrote:
> Yeap, user is important to us. lol
>
> Thanks for reviewing.
>
> Best Regards
> Sean, Xiao Xia Qiu
>
>
>
>
> 2009/5/22 Tim Ellison <t....@gmail.com>:
>> Oliver Deakin wrote:
>>> And a follow up reminder - we are now in code freeze and testing period,
>>> aiming to publish M10 on Friday 29th May.
>>>
>>> As usual, defining a bug as "must-fix" in this milestone requires (at
>>> least) two committers agreement. Please raise test failures on the list
>>> and open JIRAs where appropriate.
>> What time does the code freeze start today ;-) ?
>>
>> I'd like to propose that HARMONY-6074 patch is applied since it is
>> blocking Maven. The patch looks fine to me.
>>
>> Regards,
>> Tim
>>
>>
>>> Tim Ellison wrote:
>>>> Just a reminder. We are entering feature freeze now, and there is just
>>>> one week left to go to our code freeze date.
>>>>
>>>> No major new functionality gets dropped in from now until after M10.
>>>> Point bug fixes are still ok, and if you have time to do some testing
>>>> and fixing ahead of the test phase all the better.
>>>>
>>>> Feature freeze Fri 15th May
>>>> Code freeze Fri 22nd May
>>>> Publish Fri 29th May
>>>>
>>>> With the 'customary' definitions of what they mean.
>>>>
>>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>>> package listed in the Versions column to see those targeted for M10.
>>>>
>>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>>
>>>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Sean Qiu <se...@gmail.com>.
Yeap, user is important to us. lol
Thanks for reviewing.
Best Regards
Sean, Xiao Xia Qiu
2009/5/22 Tim Ellison <t....@gmail.com>:
> Oliver Deakin wrote:
>> And a follow up reminder - we are now in code freeze and testing period,
>> aiming to publish M10 on Friday 29th May.
>>
>> As usual, defining a bug as "must-fix" in this milestone requires (at
>> least) two committers agreement. Please raise test failures on the list
>> and open JIRAs where appropriate.
>
> What time does the code freeze start today ;-) ?
>
> I'd like to propose that HARMONY-6074 patch is applied since it is
> blocking Maven. The patch looks fine to me.
>
> Regards,
> Tim
>
>
>> Tim Ellison wrote:
>>> Just a reminder. We are entering feature freeze now, and there is just
>>> one week left to go to our code freeze date.
>>>
>>> No major new functionality gets dropped in from now until after M10.
>>> Point bug fixes are still ok, and if you have time to do some testing
>>> and fixing ahead of the test phase all the better.
>>>
>>> Feature freeze Fri 15th May
>>> Code freeze Fri 22nd May
>>> Publish Fri 29th May
>>>
>>> With the 'customary' definitions of what they mean.
>>>
>>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>>> package listed in the Versions column to see those targeted for M10.
>>>
>>> [1] http://issues.apache.org/jira/browse/HARMONY
>>>
>>> Regards,
>>> Tim
>>>
>>>
>>>
>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Tim Ellison <t....@gmail.com>.
Oliver Deakin wrote:
> And a follow up reminder - we are now in code freeze and testing period,
> aiming to publish M10 on Friday 29th May.
>
> As usual, defining a bug as "must-fix" in this milestone requires (at
> least) two committers agreement. Please raise test failures on the list
> and open JIRAs where appropriate.
What time does the code freeze start today ;-) ?
I'd like to propose that HARMONY-6074 patch is applied since it is
blocking Maven. The patch looks fine to me.
Regards,
Tim
> Tim Ellison wrote:
>> Just a reminder. We are entering feature freeze now, and there is just
>> one week left to go to our code freeze date.
>>
>> No major new functionality gets dropped in from now until after M10.
>> Point bug fixes are still ok, and if you have time to do some testing
>> and fixing ahead of the test phase all the better.
>>
>> Feature freeze Fri 15th May
>> Code freeze Fri 22nd May
>> Publish Fri 29th May
>>
>> With the 'customary' definitions of what they mean.
>>
>> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
>> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
>> package listed in the Versions column to see those targeted for M10.
>>
>> [1] http://issues.apache.org/jira/browse/HARMONY
>>
>> Regards,
>> Tim
>>
>>
>>
>
Re: [general] Milestone 10 - Code Freeze
Posted by Oliver Deakin <ol...@googlemail.com>.
And a follow up reminder - we are now in code freeze and testing period,
aiming to publish M10 on Friday 29th May.
As usual, defining a bug as "must-fix" in this milestone requires (at
least) two committers agreement. Please raise test failures on the list
and open JIRAs where appropriate.
Regards,
Oliver
Tim Ellison wrote:
> Just a reminder. We are entering feature freeze now, and there is just
> one week left to go to our code freeze date.
>
> No major new functionality gets dropped in from now until after M10.
> Point bug fixes are still ok, and if you have time to do some testing
> and fixing ahead of the test phase all the better.
>
> Feature freeze Fri 15th May
> Code freeze Fri 22nd May
> Publish Fri 29th May
>
> With the 'customary' definitions of what they mean.
>
> Issues that *must* be fixed for M10 are tracked in JIRA using the 'Fix
> for' field. From the Harmony JIRA homepage [1] click on the "5.0M10"
> package listed in the Versions column to see those targeted for M10.
>
> [1] http://issues.apache.org/jira/browse/HARMONY
>
> Regards,
> Tim
>
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU