[dune-pdelab] Patches

[Christian Engwer]

I suggest to create the appropriate 2.4 branch and then we can merge
the functions patches to master.

Is there a particular reason _not to branch_ at the end of the week?

Christian

On Fri, Apr 17, 2015 at 09:27:31PM +0200, Christian Engwer wrote:
> Hi Steffen,
> 
> > do you really want to stay compatible with ALUGrid 1.52 for the next PDELab
> > release? I think we should just tell people to install the new dune-alugrid module
> > and be done with it…
> 
> it is not only alugrid. If we want to offer users a safe upgrade path,
> it would be good, if old grids work with the new interface. I have a
> branch (I'm going to push it later tonight) with basically adds the
> entity methods to the entitypointer and forwards them. By this it is
> possible to use the a non-ported grid. 
> 
> > Oh, by the way: I would suggest calling the next PDELab release 2.4. It looks
> > like we are moving to a release schedule that is in sync with the core modules,
> > and by having the same release numbers it becomes a lot easier for people to
> > pick the correct version of PDELab.
> 
> Yes, we should call it 2.4.
> 
> Ciao
> Christian
> 
> _______________________________________________
> dune-pdelab mailing list
> dune-pdelab at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-pdelab

-- 
Prof. Dr. Christian Engwer 
Institut für Numerische und Angewandte Mathematik
Fachbereich Mathematik und Informatik der Universität Münster
Einsteinstrasse 62
48149 Münster

E-Mail	christian.engwer at uni-muenster.de
Telefon	+49 251 83-35067
FAX		+49 251 83-32729