Re: Code Freeze

[Rik]

On 12/20/2018 02:47 PM, John W. Eaton wrote:
> On 12/20/18 1:35 PM, Rik wrote:
>> On 12/20/2018 09:58 AM, John W. Eaton wrote:
>>> On 12/20/18 11:45 AM, Rik wrote:
>>>
>>>> I know you are going to have limited availability starting on the
>>>> 21st.  I
>>>> propose that before you go on holiday we stop new feature coding for the
>>>> 5.0 release, and move solely to bug fixing.  The only concrete action for
>>>> that being your merge of the default branch on to the stable branch.  The
>>>> new bug reports have already been trending this direction with several
>>>> about the build system and the test suite.
>>>
>>> I'm fine with doing the merge of default to stable whenever you think it
>>> is time.  If you are ready now, I can do it today.
>>
>> Yes, let's get on with it.
>
> OK, I merged default to stable and set the version number there to
> 5.0.1.  With the new version numbering scheme described in
> etc/HACKING.md, this version indicates the stabilization period leading
> up to the 5.1.0 release.
>
> It's too late for any big chunks of code to be added to the stable version.
>
> I have also bumped the version on default to 6.0.0 (active development
> period leading up to the 6.1.0 release), so this is also the appropriate
> time to make major changes on default.
>

I took care of the other post-release tasks (item #15 at
https://wiki.octave.org/5.0.0_Release_Checklist#5.0.0_Release_Tasks). 
Specifically, I removed deprecated functions, deprecated graphics
properties, and moved the old NEWS file into etc/ and started a new NEWS file.

--Rik