Re: [Libmesh-devel] Next release

2012-11-13 Thread Kirk, Benjamin (JSC-EG311)
I'll tag trunk at 0.8.0-rc1 and package some files. Everyone start thinking about release notes - I'll be hounding you for those later. -Ben On Nov 13, 2012, at 12:25 PM, Derek Gaston wrote: > Our libMesh testing system is showing green at the moment so I think > we're good to go. > >

Re: [Libmesh-devel] Next release

2012-11-13 Thread Derek Gaston
Our libMesh testing system is showing green at the moment so I think we're good to go. On Tue, Nov 13, 2012 at 12:07 PM, Roy Stogner wrote: > > Everything simple that I've been working on is committed as of r6357, > and BuildBot seems to be happy with us on all the important corner > cases n

Re: [Libmesh-devel] Next release

2012-11-13 Thread Roy Stogner
Everything simple that I've been working on is committed as of r6357, and BuildBot seems to be happy with us on all the important corner cases now. I may be making more ParallelMesh-with-repartitioning fixes and simple API additions for a while, but as far as I'm concerned anything from r6357-636

Re: [Libmesh-devel] Next release

2012-11-09 Thread Derek Gaston
On Fri, Nov 9, 2012 at 1:47 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > > FWIW, Roy and I were having some offline discussion, and as soon as 0.8.0 > is tagged I plan to merge automake. Like the next day… > The current plan is still to distribute a "prebuilt" configure sc

Re: [Libmesh-devel] Next release

2012-11-09 Thread John Peterson
On Fri, Nov 9, 2012 at 1:47 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > FWIW, Roy and I were having some offline discussion, and as soon as 0.8.0 > is tagged I plan to merge automake. Like the next day… > > So keep that in mind, if automake is working for you then you mig

Re: [Libmesh-devel] Next release

2012-11-09 Thread Roy Stogner
On Fri, 9 Nov 2012, Vikram Garg wrote: Roy,       Should we shoot for some kind of time dependent adjoint support before the release ? I think we have a first iteration of how to add that functionality figured out.  If we can get the first-pass stuff done and debugged before John's fixed that

Re: [Libmesh-devel] Next release

2012-11-09 Thread Vikram Garg
Roy, Should we shoot for some kind of time dependent adjoint support before the release ? I think we have a first iteration of how to add that functionality figured out. Thanks. On Fri, Nov 9, 2012 at 3:47 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > > On Nov 9, 201

Re: [Libmesh-devel] Next release

2012-11-09 Thread Kirk, Benjamin (JSC-EG311)
On Nov 9, 2012, at 2:33 PM, John Peterson wrote: > At this point, I'm fairly convinced that the only way to do shared library > linking **portably** is with libtool, but I haven't started on this patch > yet...and it will likely take a few iterations to get correct. FWIW, Roy and I were havin

Re: [Libmesh-devel] Next release

2012-11-09 Thread John Peterson
On Fri, Nov 9, 2012 at 1:15 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > OK, reviving this thread. I've got one more change I'd like to roll in of > 0.8.0 - the RB I/O optimization - but beyond that it looks like we are > pretty close. > > What else is still outstanding bef

Re: [Libmesh-devel] Next release

2012-11-09 Thread Roy Stogner
On Fri, 9 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > OK, reviving this thread. I've got one more change I'd like to roll > in of 0.8.0 - the RB I/O optimization - but beyond that it looks > like we are pretty close. > > What else is still outstanding before a feature freeze/release? I've got

Re: [Libmesh-devel] Next release

2012-11-09 Thread Kirk, Benjamin (JSC-EG311)
On Oct 25, 2012, at 5:57 PM, Roy Stogner wrote: > > On Thu, 25 Oct 2012, Paul T. Bauman wrote: > >> 1. FEMContext work - Finish off hiding public members and putting in >> accessors. I can get this done pretty quickly so I don't think it >> would hold up a release, but nothing is broken at the

Re: [Libmesh-devel] Next release

2012-10-25 Thread Boyce Griffith
On 10/25/12 9:30 PM, Kirk, Benjamin (JSC-EG311) wrote: > > On Oct 25, 2012, at 7:53 PM, Boyce Griffith wrote: > >> On 10/25/12 6:49 PM, Roy Stogner wrote: >>> On second thought, this idea gets less stupid if your "buddy" isn't a >>> human being. We could always do what a lot of other projects d

Re: [Libmesh-devel] Next release

2012-10-25 Thread Kirk, Benjamin (JSC-EG311)
On Oct 25, 2012, at 7:53 PM, Boyce Griffith wrote: > On 10/25/12 6:49 PM, Roy Stogner wrote: >> On second thought, this idea gets less stupid if your "buddy" isn't a >> human being. We could always do what a lot of other projects do and >> auto-upload a "nightly" snapshot. The last thing Build

Re: [Libmesh-devel] Next release

2012-10-25 Thread Boyce Griffith
On 10/25/12 6:49 PM, Roy Stogner wrote: > On second thought, this idea gets less stupid if your "buddy" isn't a > human being. We could always do what a lot of other projects do and > auto-upload a "nightly" snapshot. The last thing BuildBot could do > after a revision passes all tests is "make

Re: [Libmesh-devel] Next release

2012-10-25 Thread Vikram Garg
We have the following support for adjoints. Roy/Paul please correct/add/expand as you see fit. Fully coupled or single-physics problems: 1) Adjoint refinement based error estimators (Global bounds for | Q(u) - Q(u_h) |, Adjoint Example 4 ) 2) Adjoint refinement based error indicators (Adjoint Exam

Re: [Libmesh-devel] Next release

2012-10-25 Thread Cody Permann
Ah, yes my mistake. I didn't mean Makefile, but I think you all figured out what I meant. Just wanted to maintain old behavior as much as possible from the user perspective. I don't particularly have any strong opinions on exactly how we generate those files (something akin to our current bootstr

Re: [Libmesh-devel] Next release

2012-10-25 Thread Roy Stogner
On Thu, 25 Oct 2012, Paul T. Bauman wrote: > 1. FEMContext work - Finish off hiding public members and putting in > accessors. I can get this done pretty quickly so I don't think it > would hold up a release, but nothing is broken at the moment. We are > storing redundant FE info (not much) until

Re: [Libmesh-devel] Next release

2012-10-25 Thread Paul T. Bauman
On Thu, Oct 25, 2012 at 5:36 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > > But basically I'd like to freeze features for a bit to clean up for a > release Of the several features/changes I've worked on the past few months, here's the current status of incomplete stuff (th

Re: [Libmesh-devel] Next release

2012-10-25 Thread Roy Stogner
On Thu, 25 Oct 2012, Roy Stogner wrote: > The only alternative would seem to be insisting that users work on > the "buddy" system, wherein if you can't build autotools yourself > you find someone who can to ship you a "make dist" when you need an > update... On second thought, this idea gets les

Re: [Libmesh-devel] Next release

2012-10-25 Thread Paul T. Bauman
On Thu, Oct 25, 2012 at 5:43 PM, Roy Stogner wrote: > > For release versions, we ought to be able to upload the output of > "make dist", right? That has configure and everything.in > pregenerated, yet it ought to still include the .ac and .am files for > anyone who wants to monkey with the build

Re: [Libmesh-devel] Next release

2012-10-25 Thread Derek Gaston
On Thu, Oct 25, 2012 at 4:43 PM, Roy Stogner wrote: > > What do we do about people who want to follow svn, though? I'd vote > for our current "check in the results of ./bootstrap" policy, despite > the results being slightly more voluminous. I vote for this. Anyone should be able to checkout a

Re: [Libmesh-devel] Next release

2012-10-25 Thread Roy Stogner
On Thu, 25 Oct 2012, Paul T. Bauman wrote: > IMO, it should ship with a configure (built from the bootstrap) and > the bootstrap script (really just autoreconf). configure will > generate the Makefiles and the user doesn't need autotools, but if > user wants to monkey with the build system, they

Re: [Libmesh-devel] Next release

2012-10-25 Thread Kirk, Benjamin (JSC-EG311)
On Oct 25, 2012, at 5:35 PM, "Paul T. Bauman" wrote: > On Thu, Oct 25, 2012 at 5:31 PM, Cody Permann wrote: > > 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. > > IMO, i

Re: [Libmesh-devel] Next release

2012-10-25 Thread Paul T. Bauman
On Thu, Oct 25, 2012 at 5:31 PM, Cody Permann wrote: > > 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. > IMO, it should ship with a configure (built from the bootstrap) an

Re: [Libmesh-devel] Next release

2012-10-25 Thread Kirk, Benjamin (JSC-EG311)
>> 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

Re: [Libmesh-devel] Next release

2012-10-25 Thread Cody Permann
On Oct 25, 2012, at 4:10 PM, Roy Stogner wrote: > > On Thu, 25 Oct 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> 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

Re: [Libmesh-devel] Next release

2012-10-25 Thread Roy Stogner
On Thu, 25 Oct 2012, Kirk, Benjamin (JSC-EG311) wrote: > 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 rele

[Libmesh-devel] Next release

2012-10-25 Thread Kirk, Benjamin (JSC-EG311)
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? -Ben -- Everyone hates slow websites. So do w