On Fri, 1 Aug 2008, John Peterson wrote:
> Either of you know if it's possible in svn to do "backporting" of
> changes? I.e. Can I check in a change to an old, already-tagged
> revision? I searched around on the web a bit but didn't come up with
> anything promising.
I don't think so; isn't the standard workflow here to branch the code?
So you wouldn't be able to backport fixes to 0.6.2, but you could
branch off 0.6.2.1 and add the fixes there.
> For example it might be helpful if we could continue compiling
> released libmesh versions with newer versions of PETSc. (Right now for
> example, 0.5.0 needs the SNESSetMonitor -> SNESMonitorSet change in
> order to work with Petsc 2.3.3.) That way we could test an old
> codebase without also having to reinstall whatever old PETSc that
> version used to compile with.
This is a good idea. A better idea might be to release 0.6.3 soon.
I don't want to call our next release 0.7.0 (or even 0.6.9) until
ParallelMesh is in better shape with adaptivity and DiffSystem's
methods have been refactored... but it's been too long since our last
release, none of the non-experimental code should be unstable at the
moment, and it might be a good idea to get all the accumulated changes