From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] v1.4 bug review request
Date: Sat, 18 Mar 2023 08:50:56 -0700 [thread overview]
Message-ID: <CAA93jw7sswP=DAKm=y7o3jQCF-e_rf8wbVZgY1fdAb39Hn8Q9g@mail.gmail.com> (raw)
It is extremely obvious we are going to miss our March 31st ship date
for v1.4. I have been lax about getting through the
checklist, and excitedly watching all v1.5 the new development in the
heimdall branch, and busy on other matters.
We have closed 53! 53! bugs on the path to v1.4 so far. A huge hug to
everyone that helped!
The v1.4-rc2 candidate has been very stable for everyone (so far as we
know), and I am tempted to punt *all 28* the remaining bugs on the
milestone for v1.4 to the next release, or later.
But it would be very helpful if others here could burn an hour leaning
on reviewing these, comment, and see what actionable items can be
extracted (quite a few of these feel "90% done", can we close them and
create a new bug?), and especially, highlight any you feel are genuine
barriers to the v1.4 release of LibreQos. Also if you are experiencing
any new issues with v1.4-rc2, please file bugs on it!
Thank y'all for strapping yourself in to tackle this tedious task.
https://github.com/LibreQoE/LibreQoS/milestone/1
There is also the checklist here:
https://github.com/LibreQoE/LibreQoS/issues/229
If this email reminder doesn't work, we will do a videoconference to
go through them, and if that doesn't work, hot irons and bungie cords
will be distributed, and if that doesn't work...
--
Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2023-03-18 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw7sswP=DAKm=y7o3jQCF-e_rf8wbVZgY1fdAb39Hn8Q9g@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