Re: 3.8 -> 4.0 transition plans

[Reza Housseini]

On Tue, Dec 3, 2013 at 7:53 PM, John W. Eaton <address@hidden> wrote:

On 12/03/2013 01:34 PM, Jordi Gutiérrez Hermoso wrote:

Critical non-GUI fixes found in the stable release go on stable and
get forward-merged into release-gui and default. We know the GUI is
full of bugs, which is the point of the release-gui branch, so all GUI
fixes go into gui-release. Fixes that break API go into default.

Also, since we are not installing any of the headers from the libgui directory, there are few (if any) changes that we could make to the GUI that could considered to break the API.  So I think that any change to the GUI is allowed as long as it only touches files in the libgui directory.  But of course we are expecting that changes to the GUI improve stability and remove bugs, not the opposite, so let's not go too wild with redesigning and refactoring.  We can think about those things after 4.0.

jwe

I just created a new Wiki page [1]. Could we collect the findings of this conversations here?

[1] http://wiki.octave.org/Roadmap