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 <[email protected]<mailto:[email protected]>> wrote: This change: https://bitbucket.org/petsc/petsc/commits/c0decd05c6848b80907752eef350b55c8c90e696#Linclude/petscksp.hF448 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. Thanks, Matt -- 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 https://www.cse.buffalo.edu/~knepley/<http://www.cse.buffalo.edu/~knepley/>
