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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to