On Wed, Oct 28, 2015 at 12:52 PM, John Peterson <jwpeter...@gmail.com> wrote:
> > > On Wed, Oct 28, 2015 at 12:33 PM, John Peterson <jwpeter...@gmail.com> > wrote: > >> >> >> On Wed, Oct 28, 2015 at 11:34 AM, Roy Stogner <royst...@ices.utexas.edu> >> wrote: >> >>> >>> On Wed, 28 Oct 2015, Kirk, Benjamin (JSC-EG311) wrote: >>> >>> >> On Oct 28, 2015, at 11:51 AM, John Peterson <jwpeter...@gmail.com> >>> wrote: >>> >> >>> >> libmesh-0.9.4 was tagged on Feb 19, 2015, while PETSc 3.5.4 came out >>> in May >>> >> 23, 2015, so it's actually a nice surprise that this configuration >>> actually >>> >> compiles... >>> > >>> > Definitely overdue. Anything in work we need to clean up first? >>> Certainly we'll look at the performance regression just pointed out... >>> >>> Once the performance regression is fixed and the fixes for AMR on >>> multi-dimensional meshes are committed (which ought to be this >>> afternoon for both) we ought to be in good shape, IMHO. >>> >>> But man, wasn't your newest baby born like three days ago? I can see >>> how that might get you thinking about "new releases", but you can let >>> John and I handle it this time. ;-) >>> >>> If you want to be all managerial, you can be the one to decide whether >>> we christen it 0.9.5 or 1.0.0. >>> >> >> Yes, we should definitely make another release soon. Once the >> performance regression fix is merged, we can start an 0.9.5 branch with >> relevant updates to the NEWS file and the changes to configure.ac >> necessary to update the version. >> >> This branch can live for a while and have bugfixes cherry-picked over >> from master, but no new features will be added. Then once the final 0.9.5 >> is tagged, we'll merge the 0.9.5 branch back in to master like we did for >> 0.9.4 (see d1b1724), as that seemed to work pretty well... >> > > Oh yeah, I'd also like to enhance the strip_dup_libs.pl script to shuffle > /usr/lib and /usr/local/lib (anything in /usr basically?) to the end of > list of library paths before the next release. It may just be me, but it > feels like there are a lot more people experiencing issues with this > lately... > The strip_dup_libs.pl fix has been merged, and I also started an 0.9.5 branch with stuff for the next release. For some historical perspective, I also dug some of the older release dates out of the SVN archive and compiled them here: https://github.com/libMesh/libmesh/wiki/libMesh-release-history -- John
------------------------------------------------------------------------------
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
