Trans, The trunk had not been merged from MEM2 at all yet. It is still in the 0.4pre state. If the MEM2 is deemed a better stable version then I can merge back into the trunk.
We should make a project coding decision about where development happens. I prefer development in branches, the trunk always being the last stable release. I think it is probably fine for other developers to work in the MEM2 branch for now. However, many of the old patches that are waiting in the wings have either been dealt with or may no longer be applicable. I would also ask that anything that touches memory management be discussed first so as to not create problems, since my activity is through the entire code base. Dan On Sep 2, 2007, at 22:29, TRANS wrote: > On 8/30/07, Dan Janowski <[EMAIL PROTECTED]> wrote: >> libxml at rubyforge (http://rubyforge.org/projects/libxml/) now has a >> packaged development release from the MEM2 branch (New Memory Model) >> http://rubyforge.org/frs/shownotes.php?release_id=14118 >> >> The downloads are highlighted here: >> >> http://rubyforge.org/frs/?group_id=494&release_id=14118 >> >> Please be sure to read the brief release notes about running the >> tests in 'rwtest' without having to install this release. >> >> If anyone has amd64/freeBSD the rwtest/doc_file.rb seems to be >> specific to that platform. If anyone can test it, please report back. >> >> The next release should increase the coverage of MEM2 as well as >> integrating the tests in rwtest into the rake file. >> >> This release of MEM2 resolves a wide variety of bugs. > > Hey Dan, > > Which version is the MEM2 a branch of --is it the current trunk? > > Thanks, > T. > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
