[dune-pdelab] Release... to branch or not to branch

[Steffen Müthing]

Am 11.04.2014 um 16:20 schrieb Oliver Sander <sander at igpm.rwth-aachen.de>:

> Well of course we can't apply clean-up patches now that break 2.3 compatibility.
> But that doesn't mean that dune-pdelab master can be left in a state of incompatibility
> with the dune core master.
> 
> Besides, what if I tested against 2.3 with a toolchain that really does not have
> rvalue references?  I would get the same bug.
> 
> Cheers,
> Oliver
> 
> Am 11.04.2014 16:13, schrieb Christoph Grüninger:
>> Hi Oliver,
>> nice quote :-)
>> 
>> Source:
>> http://lists.dune-project.org/pipermail/dune-pdelab/2014-April/000640.html
>> http://lists.dune-project.org/pipermail/dune-pdelab/2014-April/000642.html

This is *really* not a good idea! I’m all for getting rid of the tests, but the correct way
going forward would be to simply always define the feature macros in dune-common!
Just removing the macros definitely breaks our deprecation rules...

Are there any reasons not to do have those macros in dune-common? Otherwise
I’ll prepare a patch (I’d probably tack it onto the C++11 compiler check).

Steffen


>> 
>> Bye
>> Christoph
>> 
>> 
>> 
>> _______________________________________________
>> dune-pdelab mailing list
>> dune-pdelab at dune-project.org
>> http://lists.dune-project.org/mailman/listinfo/dune-pdelab
>> 
> 
> 
> _______________________________________________
> dune-pdelab mailing list
> dune-pdelab at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-pdelab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune-pdelab/attachments/20140414/326f79a7/attachment.sig>