aglider writes "OpenWrt has been delivering in the lastes 8+ years alternative, opensource firmware for a rather large (and growing) number of devices, not just routers, like Linksys, NetGear and TP-Link just to name a few.
The latest version, like in the past 5 years, has been code-named after an alcoholic beverage, the attitude adjustment drink.
From the original announcement:
The OpenWrt Team is happy to announce the beta release of Attitude Adjustment (12.09).
This release is sligthly overdue, but it is now ready for testing.
* Improved LuCI interface
* Switch to the netifd infrastructure for better network configuration support
* Fixed Imagebuilder, relocatable SDK
* Full (?) eglibc support
* Release support for bridge firewalling
* Vastly improved ath9k driver stability and performance
* Dependency fixes for packages
* More iptables addons, improved netfilter performance
* Experimental support for 5 and 10MHz channels in ath5k and ath9k
* Support for 6RD configuration
* Experimental crashlog feature to track kernel oopses
* Reduced space requirements and improved squashfs/kernel compression
* Various package improvements and updates.
OpenWrt is a project based on a consensus decision model amongst the core team developers. With over 1000 binary packages, the Attitude Adjustment release is the biggest to date.
These 1000+ packages have the inherent problem that they need to be maintained. As the name of the release already suggests things are in a process of adjusting. The main change is that the developer group has arrived at the mutual agreement, that the packages feed is too much bloat for the project to carry around. This massive set of packages causes the developers not to have enough time for the core of OpenWrt.
The result is: The package feed is not being maintained in a way that ensures the required quality.
A couple of warnings are due here.
First, your warranty can be voided by loading those firmware into your device.
Second, it can be tricky to do so, up to needing to solder a serial console adapter into your device PCB.
Third, you won't use your stock firmware any more!"
Link to Original Source