[threeten-dev] Code Freeze tomorrow

[roger riggs]

Hi,

On 7/9/2013 3:32 PM, Stephen Colebourne wrote:
> #299 is waiting approval from Oracle that the algorithm for smart is
> acceptable as the default. (It would be awkward in some ways if it
> wasn't acceptable).
ok, I have ping'ed them to review it, if no response by tomorrow, I 
would push it
and correct it later as necessary.
>
> #282 is only open as a placeholder for more testing. That won't happen
> in the next week.
ok
>
> I think #321 is desirable, but makes our implementations harder as it
> probably results in lots of duplicate code. It won't be done this
> week. (this is a busy work week)
ok, duplicate code is not a plus, we can take another look later.

Thanks, Roger

>
> Stephen
>
>
> On 9 July 2013 20:07, roger riggs <roger.riggs at oracle.com> wrote:
>> Hi,
>>
>> It is time to integrate the accumulated ThreeTen changes into the TL
>> workspace.
>> As mentioned last week, tomorrow is the cut off for getting changes into
>> this update.
>>
>> I am working on:
>>    - #326 to cleanup up the Japanese Eras.
>>    - #292 to remove the generics from ChronoLocalDate  (web-rev later today)
>>
>> What additional changes can we expect by tomorrow?
>>
>> Can we plan to include:
>>   -  #321 Change Chronology to be an Interface?
>>   -  #282 and #299 related to lenient parsing; are these complete?
>>
>> Thanks, Roger
>>