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