Re: gui-release branch created; classdef branch merged to default and closed

[Mike Miller]

On Thu, 5 Dec 2013 12:26:01 -0500, John W. Eaton wrote:
>   * Everything else is shades of grey, but I recommend for starters:
>     fixes that change non-GUI behaviour or API go into default. Simple
>     fixes can go into gui-release, more complex changes into
>     default. The shades of grey are deciding what "simple" and
>     "complex" mean, but we can judge these on a case-by-case basis.
> 
>     WHEN IN DOUBT, ASK FOR ADVICE!

Documentation fixes are not mentioned in this plan, both function
docstrings and user manual text. My intuition is to fix them on the
stable branch, since they do not affect behavior and will improve the
3.8 release. Yes?

-- 
mike