From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Libreqos v1.4-rc1 is now available
Date: Sat, 4 Mar 2023 09:47:42 -0800 [thread overview]
Message-ID: <CAA93jw6=3MHh6LoW0Z=uS6P_U+2ER7_fgwBY88ZGTcrDf2FVGA@mail.gmail.com> (raw)
After a long period in alpha and multiple successful new installs all
over the world, we believe libreqos v1.4-rc1 is stable enough for the
less faint of heart to give it a shot. While there remain a bunch of
fit and finish (mostly) bugs left to resolve before the final release,
we're sure that no crash bugs remain (At least, we're pretty sure!).
So please give it a shot, try it in your lab at least, and file new
bugs on the github!?
Installation instructions are here:
https://github.com/LibreQoE/LibreQoS/wiki/v1.4
If you haven't been keeping up with us in the #libreqos:matrix.org
chat room, please join!?
--
Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2023-03-04 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 17:47 Dave Taht [this message]
2023-03-05 4:28 ` [LibreQoS] Libreqos v1.4-rc2 " Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6=3MHh6LoW0Z=uS6P_U+2ER7_fgwBY88ZGTcrDf2FVGA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/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