From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id C7C2821F1EA for ; Fri, 7 Feb 2014 09:45:08 -0800 (PST) Received: by mail-ob0-f169.google.com with SMTP id wo20so4390632obc.0 for ; Fri, 07 Feb 2014 09:45:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Yc/i2+NZtzW2MV0M7niOX8xtZ5S6jeOvcCJlAN+JFqA=; b=lM4KH4T9JbSh8ag/KJFqJDRKgGqBQuTFRQyGQUnZFldRDz+rLHiHHkl0lMSRfCa1hP DXlcxVdV3Jmv0j+qrOADvf85PgxRmlpqacXKdv03HsO8MYUJDbX6Fy7kQNnrdkE+HJeM KfgafFrtklYRMtJ856oiu4Y28y/Sm2dXFx6OrrvKSbiMDFDIZlbky+HoxgABnF1GfSDU n+hFkiTbjVzdRMt04M+50ZIXR7rWM8jCfEMIUNy6SWRMeC93PexmGIpXyASHtbeB2dJn dRsjiLb8sPHNo59JVi5A0NhfHiMnZCnA8tdlHHZHbOnrQk7HQJuQcOMBvEjc3UQMSO7l pzZA== MIME-Version: 1.0 X-Received: by 10.182.246.39 with SMTP id xt7mr13855278obc.16.1391795107802; Fri, 07 Feb 2014 09:45:07 -0800 (PST) Sender: gettysjim@gmail.com Received: by 10.76.84.162 with HTTP; Fri, 7 Feb 2014 09:45:07 -0800 (PST) In-Reply-To: <20140207100146.5ba027c3@samsung-9> References: <20140207100146.5ba027c3@samsung-9> Date: Fri, 7 Feb 2014 12:45:07 -0500 X-Google-Sender-Auth: mlNboYCyWqwcwR4mwMsT8jmCYHw Message-ID: From: Jim Gettys To: Stephen Hemminger Content-Type: multipart/alternative; boundary=001a11c2e2240034ec04f1d48d6d Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Will there ever be a stable version of cerowrt? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 17:45:09 -0000 --001a11c2e2240034ec04f1d48d6d Content-Type: text/plain; charset=ISO-8859-1 On Fri, Feb 7, 2014 at 12:01 PM, Stephen Hemminger < stephen@networkplumber.org> wrote: > Any progress on getting a stable version? Recent versions seem to be > targeted > at IPv6 and other things which do not impact me for home use. What does > matter > is fixing the wireless hanging issue on 2.4Ghz. > Dave's (and I) are pedalling as hard and fast as he can at the moment. And Dave has other responsibilitys that consume time. The IPv6 problem consumed a lot of time, and you do care. Comcast has lit up a big chunk of their network with Native IPv6 and tickled a latent disastrous bug (now fixed upstream in OpenWrt). That we simultaneously had a disk failure on our machine that does much of OpenWrt's and CeroWrt's builds is more than unfortunate and so we end up spending our time on trying to get the build situation fixed once and for all (by getting machines and people to set up and manage the build system going forward at a scale previously unimaginable to OpenWrt/CeroWrt). And yes, we're making progress on all fronts. 2 juicy servers are teed up awaiting a single signature (thanks Mikael!) and I have a strong lead on both large amounts of additional cloud cycles and volunteers to help admin all this so it doesn't happen again and the build system is as fast as it should be (continuous across all supported architectures) It would be very help if this mailing list could at least nominate bugs that they think are showstoppers before declaring it "soup".... But please don't jiggle the chef (Dave's) arm expecting immediate involved response in that discussion while sorting through it; it will reduce the time to see what if anything remains. We keep finding more and more people running CeroWrt (not subscribed to this list necessarily) we had no clue were doing so. I know I have one test I have to run on the first build he can give me (one Mike Frankston ran into) that might be in that category if I can easily reproduce it, as I think I ran into it myself recently. It would cause a support nightmare as it's a "new to CeroWrt" thing triggered from an obvious thing you want and often need to configure. But we gotta be able to build it, close out those show stoppers and test the fixes, and get that build installed on enough boxes in different environments for Dave send out an announcement that people should try an upgrade. We know it has to be ASAP. - Jim > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --001a11c2e2240034ec04f1d48d6d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Fri= , Feb 7, 2014 at 12:01 PM, Stephen Hemminger <stephen@networkplu= mber.org> wrote:
Any progress on getting a stable version? Recent versions = seem to be targeted
at IPv6 and other things which do not impact me for home use. What does mat= ter
is fixing the wireless hanging issue on 2.4Ghz.

Dave's (and I) are pedalling as hard a= nd fast as he can at =A0the moment. =A0And Dave has other responsibilitys t= hat consume time.=A0

The IPv6 problem consumed a lot of time, and you d= o care. =A0
Comcast has lit up a big chunk of their network with Native IPv6 and tickle= d a latent disastrous bug (now fixed upstream in OpenWrt). That we simultan= eously had a disk failure on our machine that does much of OpenWrt's an= d CeroWrt's builds is more than unfortunate and so we end up spending = =A0our time on trying to get the build situation fixed once and for all (by= getting machines and people to set up and manage the build system going fo= rward at a scale previously unimaginable to OpenWrt/CeroWrt). =A0

And yes, we're making prog= ress on all fronts. =A02 juicy servers are teed up awaiting a single signat= ure (thanks Mikael!) and I have a strong lead on both large amounts of addi= tional cloud cycles and volunteers to help admin all this so it doesn't= happen again and the build system is as fast as it should be (continuous a= cross all supported architectures)=A0

It would be very help if this = mailing list could at least nominate bugs that they think are showstoppers = before declaring it "soup"....=A0

But please don't jiggle th= e chef (Dave's) arm expecting immediate involved response in that discu= ssion while sorting through it; it will reduce the time to see what if anyt= hing remains.=A0

We keep finding more and more = people running CeroWrt (not subscribed to this list necessarily) we had no = clue were doing so.=A0

I know I have one test I have = to run on the first build he can give me (one Mike Frankston ran into) that= might be in that category if I can easily reproduce it, as I think I ran i= nto it myself recently. =A0It would cause a support nightmare as it's a= "new to CeroWrt" thing triggered from an obvious thing you want = and often need to configure.

But we gotta be able to build = it, close out those show stoppers and test the fixes, and get that build in= stalled on enough boxes in different environments for Dave send out an anno= uncement that people should try an upgrade. =A0

We know it has to be ASAP.

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 - Jim
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

--001a11c2e2240034ec04f1d48d6d--