<!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=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div style="">

<p dir="auto">These situations are always confusing. Since just the tarball has been updated from exactly the same sources, the git tag stays at 3.6.7 and the changelog doesn't change. Just overwriting the broken tarball with a new one is discouraged/disliked by many people as well.</p>

<p dir="auto">But an announcement would reduce confusion. A complete irregular 3.6.7.1 release would be the cleanest way. Other projects do stuff like that in such cases. As I will do in my projects in such future situations (I already ran into the same problem and solved it similar to how <a href="https://gitlab.com/nmav" data-user="105950" data-reference-type="user" data-container="body" data-placement="bottom" class="gfm gfm-project_member" title="Nikos Mavrogiannopoulos">@nmav</a> did - also with some confusion as the users side).</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/issues/745#note_157280063">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/f5e4d053fe191ef133ca2864c66cbb80/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 Issue","url":"https://gitlab.com/gnutls/gnutls/issues/745#note_157280063"}}</script>

</p>

</div>

</body>

</html>