<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.com/nmav">Nikos Mavrogiannopoulos</a>
commented on a
<a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1199#note_305048034">discussion</a>:
</p>
<div style="">
<p dir="auto">I'm not arguing here for not doing that, my point is about setting the rules of the game, so it is clear when we are introducing unstable APIs, how are applications are supposed to use them (if they are).</p>
<p dir="auto">For example, my expectation from the "when we introduce such APIs", would be to allow such APIs when used in collaboration with other applications (curl, wget?) to test a new TLS feature. Should we bring unstable APIs when it is not clear who is the actual user of them? I looks risky to me as it looks hard to manage variable expectations. If these APIs are broken after the standard is published, then I'd also expect not to keep compatibility with the old ones (i.e., this instability should not be accumulating technical debt) and the applications these APIs that were targeting should take this into account.</p>
<p dir="auto">Without setting by documenting these expections, this API although it allows to break the ABI as defined by the .map file, it may not necessary allow us to break that ABI if applications in popular distributions depend on the features introduced by it.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1199#note_305048034">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/sent_notifications/f38ff102aa005985fe4f7942f28c038e/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/-/merge_requests/1199#note_305048034"}}</script>
</p>
</div>
</body>
</html>