From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] wireguard-linux-compat v1.0.20200712 released
Date: Sun, 12 Jul 2020 22:06:06 -0600 [thread overview]
Message-ID: <CAHmME9qDW7CLDzQhwHQ7bb==dKAdgtbZfEtzmNaxB-atwCguag@mail.gmail.com> (raw)
In-Reply-To: <913e8149b5a5c3a6@mail.zx2c4.com>
On Sun, Jul 12, 2020 at 9:34 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> * compat: SUSE 15.1 is the final SUSE we need to support
>
> >=15.2 is in SUSE's kernel now. We'll be dropping 15.1 support in a
> few weeks after people have had time to upgrade.
As said above, SUSE backported WireGuard into their kernel for 15.2,
both on the OpenSUSE variant and on their enterprise distro. This is
terrific news.
I'm considering making this compat module release the last release
that supports the now-old 15.1 release. `zypper update` automatically
puts people on 15.2, as far as I can tell, and it seems like the
general path for SUSE is to update. Plus, people who tend to use
WireGuard tend to like to update.
I put this in the git repo a few minutes ago:
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=2a1b895ec2f529a75a6bc63fd5b6baee2b1735b3
If anybody thinks that 15.1 support would be worth preserving for more
releases (how many?), this would be the time to speak up. I'm happy to
have my presumptions about SUSE user update habits proved wrong and to
change course accordingly.
Jason
next prev parent reply other threads:[~2020-07-13 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 3:34 Jason A. Donenfeld
2020-07-13 4:06 ` Jason A. Donenfeld [this message]
2020-07-13 5:19 ` Luca Beltrame
2020-07-13 14:39 ` Samu Voutilainen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9qDW7CLDzQhwHQ7bb==dKAdgtbZfEtzmNaxB-atwCguag@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).