On Fri, 9 May 2014, Michael Povolotskyi wrote: > On 05/09/2014 11:25 AM, John Peterson wrote: > >> On Fri, May 9, 2014 at 9:08 AM, Michael Povolotskyi >> <mpovo...@purdue.edu <mailto:mpovo...@purdue.edu>> wrote: >> >> When the official release with the patch is going to happen? >> >> >> Hard to say, we aren't on a very regular release schedule. >> >> And this wasn't a regression per se, so I don't think it's worth >> rushing an official point release out the door. (I also may have >> broken some of the less-used compiler configurations which I don't >> test but I think Roy and Ben's buildbots do.) >> >> Although we probably should start the discussion since the last one >> was almost 3 months ago. > > This issue was important for us because we got conflicts between Libmesh > symbols such as DenseMatrix and our DenseMatrix class. > We simply could not compile the code. > > Before the next release we will have to carry the patch with us and > distribute it to our customers, which gives them a bad impression. > So, if the new release comes soon, we'll be very happy.
It's too soon and there's too much cleanup required ATM to get out a new "real" release right away, but we ought to backport and do a bugfix release for a regression this big. I'm swamped right now, but I'll try to get an 0.9.3.1 out next week. Any other fixes worth backporting while I'm at it? --- Roy ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
