Following up on this, the code base is now frozen until the release branch 
is cut (hopefully sometime between Friday and Monday).  While testing 
wasn't absolutely clean last night, it doesn't seem as though there were 
any fatal errors related to the code base itself, either.

During the code freeze, it's fair game to work on adding/improving 
documentation (please do! particularly for new things you added/changed 
during this release cycle) and to work on tests that are not part of the 
release.

If anyone has something that they think should be committed in spite of 
the code freeze, please speak up.

Thanks,
-Brad


On Tue, 16 Sep 2014, Brad Chamberlain wrote:

>
> Feature freeze was a week ago today; code freeze (including tests to appear 
> in the release) is scheduled for today.  Doc freeze is Friday. Hopefully we 
> cut the release branch early next week (if not Friday) and move on to 1.11).
>
> -Brad
>
>
> On Tue, 16 Sep 2014, Michael Ferguson wrote:
>
>> Hi -
>> 
>> I know we're in some kind of feature/code freeze for the release
>> but I don't know the dates of anything. Could somebody remind
>> me (or the list) of the relevant dates for bug fix freeze
>> and doc freeze?
>> 
>> Thanks,
>> 
>> -michael
>>
>> 
>> ------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce.
>> Perforce version control. Predictably reliable.
>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Chapel-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/chapel-developers
>> 
>

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to