Dealing with smoketests, release candidates and the final release

The cerowrt development process is broken up into three phases - smoketests, release candidates, and eventual release.


The smoketests will one day be daily automated builds. At present they are tests against fixed bugs, mostly.
YMMV. Do NOT work against a smoketest for anything serious.

A principal problem with smoketests is that they are totally unsupported and the package database
points at the rc catagory they will be. To get the additional packages you will need to point /etc/opkg.conf to the correct
the smoketest build directory.

Release candidates

Release candidates are the more polished, fully tested versions of cerowrt as we march down towards a release.

When will we get Cerowrt 1.0?

When all priority 1 and 2 bugs are fixed on the roadmap. Our hope was september 15, but we’ve missed that date considerably.

Oct 15 would be a good date to aim for.

To edit this page, submit a pull request to the Github repository.
RSS feed

Recent News & Articles

Sep 6, 2018 Wiki page
Pete Heist's Thoughts on ECN
Sep 5, 2018 Wiki page
Dave Taht's Stance on ECN
Sep 4, 2018 Wiki page
Jonathan Morton's Take on ECN
Sep 3, 2018 Wiki page
ECN-Sane Project
Aug 24, 2018 Wiki page
ECN-Sane Project

Find us elsewhere

Bufferbloat Mailing Lists
#bufferbloat on Twitter
Google+ group
Archived Bufferbloat pages from the Wayback Machine


Comcast Research Innovation Fund
Nlnet Foundation
Shuttleworth Foundation

Bufferbloat Related Projects

Congestion Control Blog
Lede Project (OpenWrt)
Flent Network Test Suite
The Cake shaper

Network Performance Related Resources

Jim Gettys' Blog - The chairman of the Fjord
Toke's Blog - Karlstad University's work on bloat
Voip Users Conference - Weekly Videoconference mostly about voip
Candelatech - A wifi testing company that "gets it".