From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A52313B29D for ; Wed, 1 Feb 2023 20:29:53 -0500 (EST) Received: by mail-wm1-x330.google.com with SMTP id n28-20020a05600c3b9c00b003ddca7a2bcbso235278wms.3 for ; Wed, 01 Feb 2023 17:29:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7sY76SPJ4HcI2mXkgNG+ZceLjoH0k9mskPchHEAJc2k=; b=KdsW6sM+gYOSALgH/0fl79kT3grQA04AYz19ooZznKrqAhcnZVD5yEKZJLgj/yqWvI i7fRJOED8ziPoKups7NAHSXMYQQK0ShQ3WHSct5IgMHlMHY5/jOB6TMg7SV4tbNYaP/A M9U3d9V/gityQZ1dvS8v9Wq8dJgwFxA1nlufDlIX2x4txJRizvJPXUHx7j9z+JLJudjS spX1q85axD7WK1gUarW00obUkNqb+zsJj4TcNsugW4BHkDs2+zhh5dhBcO+rskNKkfDC i8cyXA+0e0bNDDMEtIERafGIrmuDV5ftscrJxs1rMxlunkJh/ZOUpi7kbwZMd1IuMEPD 3bVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7sY76SPJ4HcI2mXkgNG+ZceLjoH0k9mskPchHEAJc2k=; b=gcFIrfPKjwEM6/BaYIqODh50pgm3+Q30J9itzH4OSt0t5ztqsSAl8OsLmHwwRYaj1c bgosjqPDbVI/Mv/avvXm0WPZbRndX77tcoTknFqvrM6DjMU70tyMykWHzQ0KIwbGt9om xeZwdtYVecKswmxFvGwkPkIuyTWSG7l2q1tkcXVytZYklBkB/dfMy1NP07zZ/5rj42Nm xCEgllYXSxfxL1W8vM6etNixQGTlZIZE81ossBFMIQte07Kp92mDT8WlRk5osaN3hmwE 94he6qPmURKgYBrILw8NQTWuNLCSmAdGV4WgDV/wQT9V4uPM+Jr8lK+9oTR3ccWcIB2d E7hw== X-Gm-Message-State: AO0yUKVKu0nebePPWn4VubNzF1iLrt6IqC50ZbPbfkSGjVi94YwSp7m2 SgZyX/h428YHBctQTgJeb/x/4nscTv5gZgIsGwYGPT5+v1o= X-Google-Smtp-Source: AK7set9dL+Cw4lKxWokvmR7tFN1tkwge8vk+POi/egh/UISK/OZ8FONS1GxM+VmEL7wJ41SjNpT90YBXbkWIabMvwbA= X-Received: by 2002:a05:600c:310c:b0:3dd:1ca4:9bf4 with SMTP id g12-20020a05600c310c00b003dd1ca49bf4mr49030wmo.205.1675301391696; Wed, 01 Feb 2023 17:29:51 -0800 (PST) MIME-Version: 1.0 From: Dave Taht Date: Wed, 1 Feb 2023 17:29:39 -0800 Message-ID: To: libreqos Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [LibreQoS] a milestone, of sorts X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Many ISPs need the kinds of quality shaping cake can do List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2023 01:29:53 -0000 Today, we hit 50% closed bugs for the v1.4 release cycle. My congratulations to everyone for pitching in, coding, testing, and breaking things, as things are looking a great deal more stable *and robust* than they were only a week or two ago. I am always amazed at herbert's productivity, and interduo's ability to break things, and at the NZ teams=C2=B4 willingness to test in production stuff that merely compiles. Tomorrow (thursday) at 1PM PST we have a meeting to discuss the state of the project. Presently we have not picked a technology (most of our work has moved to our #libreqos:matrix.org chat room) to have that in, I used to use my public galene server. So the cup is half full now. Or as I in general, tend to channel eyore, half empty. Of the remaining 28 bugs, many are in states of completion in the 80-99.99% range. Some are kind of complex and ideally the non-done bit, could get pulled out, and re-bugged (is that a word?). Others are overly vague. Others can just be punted to the next release. The schedule for the next release has already been slipped to march 31st, rather than March 7th. There seems to be some architectural rework needed as well, which is something that often happens at this stage of the project, where going forward, requires a step or two back. If half the folk on this list could review the bottom half up, and the other half, top half down, of what remains, we could meet in the middle: https://github.com/LibreQoE/LibreQoS/milestone/1 And for those of you that have not been tracking progress so far, please se= e: https://github.com/LibreQoE/LibreQoS/milestone/1?closed=3D1 And for those of you here that had a grand dream of THE KILLER FEATURE that will bring all ISPs more sleep and profits, and the devteam a paycheck... we have punted a great deal of stuff already to the v1.5 release: https://github.com/LibreQoE/LibreQoS/milestone/3 or a complete blocker for their adoption of v1.4... and have not communicated what it is - More suggestions for that or future milestones welcomed on this list, or on the github, or via the chat room. I would love a definition of the killer feature(s) for this release that works. Herbert=C2=B4s new bifrost bridge in particular is benching out at 30% or more faster than the original code. Donations are being accepted on our github sponsors page, if you or some org you know of, is willing to pitch in, as we slog forward. We are in need of a decent javascript programmer in particular, and at least one more python and rust programmer as well, if you know anyone. We are also on a quest to find someone(s) that can help move some high speed routines to c and rtnetlink. --=20 This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656= 07352320-FXtz Dave T=C3=A4ht CEO, TekLibre, LLC