LEDE 17.01 Testing for release

I've installed 17.01 snapshots on wrt1200 and wrt1900acs by sysupgrade with "keep settings" and had no issues. As I was using several LEDE master snapshots before I am not surprised ;-).

What can I do to properly test lede 17.01 for the upcoming release?
What tests will help developers?

If you have an older ath9k device (e.g. TP-Link TL-WR1043ND v1), there have been problems with the radio (which should be fixed now). The more people can test it, the more we're sure this is fixed before release.

1 Like

Sorry, I do not have a TP-Link.

I do. The same exact version. I can test it if you tell me how to build it.
I came across this tutorial https://lede-project.org/docs/guide-developer/quickstart-build-images
Will it suffice to just follow it and build the firmware?

Just download the snapshot here: https://downloads.lede-project.org/releases/17.01-SNAPSHOT/targets/ar71xx/generic/

Have been testing LEDE 17.01 SNAPSHOT r3040-70a6bbd on MR3420V1, MR3420V2 and WR1043NDV1 with heavy torrrents (AP Mode).
No issues as of 2 days.

Anyone knows when we can expect a stable release of LEDE?
From this thread title I assume it's soon-to-be-ready thing?

17.01.0-rc1 has been tagged already.


But I am not sure if the image build has been launched.

@jow published information about where the release candidates and final builds will be available. See: http://lists.infradead.org/pipermail/lede-dev/2017-January/005573.html

And if you want to watch history/sausage being made, check out the /releases directory at http://downloads.lede-project.org/releases/

The buildbot has already pushed out builds for au1000...

I think they are being build/published right NOW.
Thank you.

"I instructed the buildbot to produce tagged rc1 builds today, those will
be true, fixed release candidate images which do not move."

What does it mean "do not move"?

I think that there was a two day delay in the image build as the tagging script failed and needed a fix.

"do not move" means that the tag has a permanent commit hash (instead of the moving HEAD of the 17.01 branch), and the tag also sets a fixed commit hash for each of the feed definitions. In practice this means when you checkout the rc1 tag later, all feeds like LuCI, packages, routing etc. are automatically set to the fixed commit in the feed, instead of HEAD.

That change was made in the tagging commit I linked. Here the changes are shown more clearly:

src-git packages https://git.lede-project.org/feed/packages.git^31d89be9e69bac261bfe7440512cb4e0f3356255
src-git luci https://git.lede-project.org/project/luci.git^472dc4b9e2ca71c114f5da70cb612c1089b8daa7
src-git routing https://git.lede-project.org/feed/routing.git^a6c7413594a0e4b42dab42bb5fa68534e39b7d0c
src-git telephony https://git.lede-project.org/feed/telephony.git^1f0fb2538ba6fc306198fe2a9a4b976d63adb304

It has always been a challenge to explain to users who want to build the exact "release CC15.05.1" etc. that it is not enough to check the main branch sources from that release date, but also the feeds need to be from the same date.

Great that Jo automated the fixing of it for LEDE.

1 Like

Hi, I want to compile LEDE version 17.01.0 but what url for git?

git clone https://git.lede-project.org/source.git ?


To answer just that question I wrote this thread yesterday....

1 Like


I just installed LEDE 17.01 RC1 onto my TPLink MR3220V1 , so far so good but I can't install SQM as i suspect there's not enough RAM to do so

Will LEDE final release to include SQM in the firmware?

Thank you

Release candidates are primarily meant to find and ideally fix bugs before the final release, I wouldn't expect there to be changes in regards to the installed package set or significant differences in regard to flash or RAM usage/ utilization. Devices with just 4 MB flash/ 32 MB RAM are seriously challenged when it comes to running current software, imagebuilder might help you to squeeze in your missing packages this time - or it might still remain to be too large, but it's worth testing.