User Tools

Site Tools


about:latest

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
about:latest [2013/07/14 08:34]
about:latest [2016/09/17 14:45] (current)
wigyori [Bleeding Edge]
Line 1: Line 1:
 +====== Choosing an OpenWrt Version ======
 +
 +The general method for picking the right image is to visit the [[:​toh:​start|Table of Hardware]], then search for your device. Supported devices will have a //Details Page// that gives instructions for installing the most recent stable firmware for your device.
 +
 +If there isn't a Details Page or a pre-built image for your device, follow the [[doc:​howto:​build|Building OpenWrt]] instructions to build a custom image.
 +
 +Any bugs in the firmware should be reported via the [[https://​dev.openwrt.org/​timeline|ticket system]]. Before reporting a new bug please first search for similar bugs.
 +
 +===== Stable releases =====
 +
 +If you are a newcomer to OpenWrt, you should install the current stable release. The [[about:​history]] page lists all stable releases so far, and the Details Page for your router (check the [[toh:​start|Table of Hardware]]) should tell you which image to download and how to install.
 +
 +The current stable release is **Chaos Calmer 15.05.1** released in March 2016.
 +  * Downloads: https://​downloads.openwrt.org/​chaos_calmer/​15.05.1/​
 +  * Release notes: https://​forum.openwrt.org/​viewtopic.php?​id=63415
 +
 +===== Community Releases =====
 +
 +Some forum members provide custom OpenWrt Images. Visit [[https://​forum.openwrt.org/​viewforum.php?​id=16|OpenWrt Community Releases]] for more. 
 +
 +===== Bleeding Edge =====
 +
 +The development branch (trunk / master), code named **Designated Driver**, contains bleeding edge source code for OpenWrt. Currently the most recent source code is available at Github ([[https://​github.com/​openwrt/​openwrt]]) instead of git.openwrt.org (or svn.openwrt.org).
 +
 +|{{:​meta:​icons:​tango:​48px-dialog-warning.svg.png?​nolink&​24}}| The development branch can contain experimental code that is under active development and should not be used for production environments. Trunk images may support additional hardware; however, it is experimental,​ considered unstable, and sometimes won't compile. |
 +
 +
 +Bleeding edge can be built from sources:
 +
 +  * [[https://​github.com/​openwrt/​openwrt|Buildroot Sources]] ([[https://​github.com/​openwrt/​openwrt/​commits/​master|Recent Changes]])
 +
 +Alternatively,​ pre-built snapshots are available. The so-called [[http://​buildbot.openwrt.org:​8010/​|buildbots]] are automated machines that run build scripts around the clock to keep recent snapshots available for install.
 +
 +  * [[http://​downloads.openwrt.org/​snapshots/​trunk/​|Snapshot Images]]
 +
 +|{{:​meta:​icons:​tango:​48px-dialog-warning.svg.png?​nolink&​24}}| **Prebuilt trunk images do not come with any web interface or GUI**. You will need to be comfortable using a command line and remote shell to install one yourself: [[doc:​howto:​luci.essentials|How to install LuCI]] ​ |
 +
 +While the build process is automated and is mostly functioning,​ it's highly advisable that you **check the dates on the files** before downloading them to prevent installing an outdated version.
 +
 +If opkg is complaining that the packages list is too old, it is possible that the last few buildbot runs have failed for your platform and the packages are already a few days old. 
 +
 +Buildbot also reports which packages fail to build, so that developers get feedback on possible errors. So when wondering why a package is not currently available in trunk, you could also check the "​broken packages"​ list for your platform.
 +[[http://​buildbot.openwrt.org:​8010/​broken_packages/​]]
 +
 +E.g. for ar71xx: [[http://​buildbot.openwrt.org:​8010/​broken_packages/​ar71xx/​]]
 +
 +===== Older Releases =====
 +Please visit [[about:​history|the version history page]] for an overview of previous releases.
 +
 +
 +===== File naming =====
 +Please see the notes and explanations here: [[doc/​howto/​obtain.firmware.download#​file naming]]
 +
 +