On Fri, 2007-12-07 at 06:51 -0600, Barton Willis wrote:
> If somebody wants to put my FE code in the release branch, that's OK.
> I don't know how to do this.
I just did it. I also put Dan Gildea's change to macsys.lisp in the
release branch, because it is a minor change that seems useful: it
removes the message "this is a development version of Maxima" from the
start-up messages.
I also committed to the HEAD branch some changes that Andrej made in the
release branch. From my experience with previous releases, if those
changes are committed only to the release branch, they will not make it
to the HEAD cvs after the release.
I will write here a mini how-to with the process I use for working with
the release branches. I do not put it in the wiki yet, because perhaps
I'm doing something wrong or there are better ways to do it:
1- After the creation of the release branch is announced, I make a fresh
new copy of the CVS repository, with the release branch:
cvs -d :ext:villate at maxima.cvs.sourceforge.net:/cvsroot/maxima co -r
"RELEASE-5_14_0-BRANCH" maxima
2- I continue making changes and committing them in the old repository
(with the CVS head branch). If a change should also be in the release
branch and I think it is safe to put it there, I will copy the file to
the copy of the release branch and commit it there too.
Regards,
Jaime Villate