We have a few ParallelMesh changes that we haven't committed yet... but they will be going in today or tomorrow.
The work on ParallelMesh will continue... but it's not critical to wait on any of it for release. We always use libMesh from SVN anyway. Actually I've been meaning to mention that we are actually lagging our user's access to libMesh SVN. We have a local SVN repo with libMesh in it that periodically (when we know everything is working in libMesh head) updated to libMesh HEAD. Note that we don't _ever_ commit changes to this local repo... it's just meant as a buffer in between libMesh head and our users. All of the developers of MOOSE are always using libMesh HEAD though... so we stay up to date. This system has worked pretty well for us for the past few months. Derek On Apr 13, 2011, at 1:17 PM, Roy Stogner wrote: > > I'd like to put out a libMesh-0.7.1 release in the next week or two, > partly for the selfless reason that the upcoming Tet::is_child_on_side > fix may be important for other people's apps' meshes, but mostly for > the selfish reason that the new variable-upgrading restart feature is > important for our group's apps' physics. > > Is there anyone who's got not-yet-ready code in the trunk at the > moment? I know rbOOmit is in a bit of flux right now and NemesisIO is > about to be.. but is the current revision good enough to release? > > How about any outstanding bugs? I'm about to fix a race condition > that occurs when multiple libMesh apps try to read the same .bz2/.xz > input at once... anyone know of anything else? > > The tentative plan is to release 0.7.2 in ~5 months, so anything that > misses this release will get into the next one soon enough. I'd like > to stay in the habit of getting a tarball out twice a year; no more > year-plus droughts like we had between 0.5.0 and 0.6.0. > --- > Roy > > ------------------------------------------------------------------------------ > Forrester Wave Report - Recovery time is now measured in hours and minutes > not days. Key insights are discussed in the 2010 Forrester Wave Report as > part of an in-depth evaluation of disaster recovery service providers. > Forrester found the best-in-class provider in terms of services and vision. > Read this report now! http://p.sf.net/sfu/ibm-webcastpromo > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
