[petsc-dev] Deprecation strategy for Enums

Zhang, Junchao jczhang at mcs.anl.gov
Tue Apr 9 13:37:05 CDT 2019

We should have a mechanism to auto-detect API-breaking commits and then we can fix them before release.

--Junchao Zhang

On Tue, Apr 9, 2019 at 12:39 PM Matthew Knepley via petsc-dev <petsc-dev at mcs.anl.gov<mailto:petsc-dev at mcs.anl.gov>> wrote:
This change:


breaks the current LibMesh, and I am assuming other things. Do we have a deprecation strategy for this? How about we #define that old name to the same value for one release? We could do this
in 3.11.1.



What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
-- Norbert Wiener

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190409/84a16863/attachment-0001.html>

More information about the petsc-dev mailing list