[LLVMdev] [RFC] Developer Policy for LLVM C API

[Andrew Wilkins]

On Sat, 18 Jul 2015 at 03:41 Juergen Ributzka <juergen at apple.com> wrote:

> Hi @ll,
>
> a few of us had recently a discussion about how to manage the C API and
> possible policies regarding addition, maintenance, deprecation, and removal
> of API.
>
> Even thought there is a strong agreement in the community that we
> shouldn't break released C API and should be backwards compatible, there
> doesn’t seem to be a developer policy that backs that up. This is something
> we should fix.
>
> I was wondering what the interested parties think of the current approach
> and what could/should we improve to make the use and maintenance of the C
> API easier for users and the developers alike.
>
> I was hoping we could also introduce a process that allows the removal of
> an API after it has been deprecated for a whole release and the release
> notes stated that it will be removed.
>

I think a good first step would be for someone to write tests for the
stable API. Once written, these tests must not be changed (excepting bugs
in the tests) without going through the deprecation/change process.

Thoughts? Comments?
>
> Cheers,
> Juergen
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150718/b59533a8/attachment.html>