Re: Release 3.4.1

[Rik]

> 
> So given this mistake and the fact that the majority of changes since
> 3.4.0 are bug fixes or minor improvements, I think it would be best to
> just merge the release-3.4.x branc with default, then create a stable
> branch and prepare for the 3.4.1 release on the stable branch, then
> proceed with the stable/default development workflow that we've been
> discussing.  We can make it clear in the release notes for 3.4.1
> that it is unfortunately not binary compatible with 3.4.0.  In the
> future, any .oct file built for an Octave release 3.4.x should work
> with any later release in the 3.4.x series.
This sounds good to me.  When do you want to attempt the merge and split?
We can certainly hold off committing changes around that time so that the
new patches make it on to the correct branch.

--Rik