[petsc-dev] Deprecation strategy for Enums

Zhang, Junchao jczhang at mcs.anl.gov
Tue Apr 9 17:19:22 CDT 2019

I will try that to see if it works.
--Junchao Zhang

On Tue, Apr 9, 2019 at 5:14 PM Smith, Barry F. <bsmith at mcs.anl.gov<mailto:bsmith at mcs.anl.gov>> wrote:


     Do you want to give this a go? Maybe it is a script in lib/petsc/bin/maint or a makefile rule that takes two git branch names and reports any changes between them (presumably by running ./configure && make twice to generate the libraries and making a copy of one branches includes so they can be compared with the other)


> On Apr 9, 2019, at 4:42 PM, Jed Brown via petsc-dev <petsc-dev at mcs.anl.gov<mailto:petsc-dev at mcs.anl.gov>> wrote:
> "Zhang, Junchao via petsc-dev" <petsc-dev at mcs.anl.gov<mailto:petsc-dev at mcs.anl.gov>> writes:
>> We should have a mechanism to auto-detect API-breaking commits and then we can fix them before release.
> We should have our CI system flag PRs that fail this checker to confirm
> that it's documented in changes/dev.html and that the change is really
> necessary.
> https://lvc.github.io/abi-compliance-checker/

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

More information about the petsc-dev mailing list