The OpenWrt project source code is stored inside a git tree which contains all branches and releases ever made.
All repositories can be browsed online through:
Any OpenWrt development happens in the main
openwrt.git repository which is accessible via both HTTP and HTTPS:
git clone https://git.openwrt.org/openwrt/openwrt.git
You can find a mirror of the repository on Github:
git clone https://github.com/openwrt/openwrt.git
These are the folders you can find in the project’s git:
Generating Releases has already been vastly automated. The remaining parts of the process need to also be automated before the first LEDE release. We will introduce a TESTERS file that is formatted similarly to the MAINTAINERS file of the kernel. Community members can list themselves as testers for a target/profile/device. Once a release has been generated testers should receive an email informing them of the requirement for images to be tested. It needs to be decided if only tested images should be included in the binary release.
See the TODO page for more info.
To create yourself a staging tree on git.openwrt.org (does not apply to regular users):
ssh [email protected] "create openwrt/staging/yournick" ssh [email protected] "desc openwrt/staging/yournick Staging tree of Your Name"
To get your staging tree visible at https://git.openwrt.org:
ssh [email protected] "perms openwrt/staging/yournick + READERS gitweb"
To get your staging tree read accessible to everyone:
ssh [email protected] "perms openwrt/staging/yournick + READERS @all "
It has proven impractical and a waste of time to always be on the very latest kernel within 2 days of its release. It has caused the following:
Obviously, this doesn't excuse old, dusty kernels. A balanced path between the 2 should be taken that gives the community recent kernels without causing unnecessary workload and stability issues.
There should be a max of three concurrent kernel versions. Having only two concurrent versions is better than three.
In Short - stability should be valued higher than bleeding edge. Bleeding edge is important – but not as a trade-off to stability.
Adding a new device General information about adding a new device