>> Im thrilled with all the recent trunk activity, and I've got some >> major changes id like to implement soon, but first - anything >> outstanding before we create a new release? > > If you're still planning to merge automake before the next release, > I'd like that to sit in trunk for a while first to see how loud > everybody screams.
I'm not. Specifically, my plan 1.) this release 2.) merge automake 3.) move to github if that is the consensus It is easy to sync trunk and its complete revision history to github, but with complex branches and tags it gets difficult. So I like Cody's suggestion that just came in > Are there plans to distribute a prebuilt "default" Makefile? Users > could always generate there own, especially if they want out of tree > builds or have an odd system. but that can be after this release. > There's some ParallelMesh+AMR issues that are tripping failures for > us. Not new bugs, just newly-exposed bugs, though, so I wouldn't say > this is a showstopper. It is something I'm close to fixing, though, > if that's worth the wait. > > There's bugfixes for the no-MPI and --enable-complex configurations > that I need to get in and test; shouldn't take more than a day or two. > > There's a barebones-configuration test failure that I haven't looked > into yet. Thanks. I'll see if I can snoop the PECOS buildbot results and help where I can. But basically I'd like to freeze features for a bit to clean up for a release (your request ongoing in parallel, Dave.) -Ben ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
