22.03.0-rc1 has been announced. Not yet the final release, but a release candidate.
Thanks for this! I have a couple of questions, which I think others may be interested in.
For OpenWrt newbies like me what's the significance of a release candidate vs a release or stable release?
Also how does release use compare with snapshot use for the many of us completely new to OpenWrt based on the RT3200? Hitherto packages would stop being able to be installed based on kernel issue requiring new snapshot install to install new packages or upgrade. How is that affected with release.
Also in terms of upgrading how does that work? Can we restore from saved config?
Simply sysupgrade with config intact. There is no major difference between master and 22.03 for RT3200/E8450.
22.03 is practically the master of mid-March 2022. Not yet much deviations from master snapshots since then.
See Belkin RT3200/Linksys E8450 WiFi AX discussion - #2031 by hnyman
The final 22.03.0 release will be made from the same 22.03 branch as the rc1 now. There may be more small fixed before the release, but in general the RCs are pretty much the same that the final release will be.
1 Like
So for those of us really just wanting stable use we should switch over using command above?
Actually can we use auc to install the new 22.03 rc1? If so how? Sorry if this is not even a valid question. But I'm imagining saves having to download/install all already installed extra packages?
root@OpenWrt:~# auc -b 22.03 -B 22.03-0-rc1 -n
auc (0.2.5-2)
Server: https://sysupgrade.openwrt.org
Running: SNAPSHOT r19355-80f79beb95 on mediatek/mt7622 (linksys,e8450-ubi)
Invalid argument (22)
No idea if RC binaries are usually available in auc. (I have never used auc, as I build my own firmwares from sources.)
The rc1 binaries are available quite normally in the download repo, so you could download the image and flash it via sysupgrade and then reinstall the add-on packages.
https://downloads.openwrt.org/
Thanks. It would be nice to have convenience of auc to prevent having to manually install packages. I don't even know which extra ones I installed. Is there a command to find that out (i.e. the ones auc gets for me?).
auc has switches for release stuff:
root@OpenWrt:~# auc --help
auc (0.2.5-2)
auc: Attended sysUpgrade CLI client
Usage: auc [-b <branch>] [-B <ver>] [-c] [-f] [-h] [-r] [-y]
-b <branch> use specific release branch
-B <ver> use specific release version
-c only check if system is up-to-date
-f use force
-h output help
-n dry-run (don't download or upgrade)
-r check only for release upgrades
-F <fstype> override filesystem type
-y don't wait for user confirmation
Please report issues to improve the server:
https://github.com/aparcar/asu/issues
Certainly seems to make sense to me that if auc can be used for snapshots then it can be used for release candiates or releases too. Or am I missing something?
1 Like
Well, if the help text gives you a switch for a specific release, have you already tried this?
-B 22.03.0-rc1
1 Like
sorry, I didn't notice that you had already tried that.
Probably @aparcar or other auc maintainers will know if the rc1 release candidate gets available in auc.
2 Likes
2 Likes
Lynx, with the ease of installing the latest snapshot version in stable branch + opkg(s) via AUC, is there any sense in installing a point in time release (or release candidate)?
Why install RC1 over a 22.03-SNAPSHOT?
Edit: I think this may be outside the scope of the initial post, but I was curious what other's use cases are.
Good point. And this may be just me being an ignorant OpenWrt newbie, but am I not correct in thinking that an rcX is more stable than a stable branch snapshot? @hnyman could you please comment on that?
I have been using master snapshots because for RT3200 nothing else was available. But I actually use x3 of these for business use and stability is particularly desirable for me (albeit admittedly things have been extremely stable so far on even the master snapshots, so all of this may be theoretical, but I am still interested anyway).
The pretty much only major reason is if you want to later install kmods from the download repo without re-flashing the main firmware. The snapshot goes forward and kmod compatibility weakens as time goes on, but stays intact in the static release.
Other imaginable reason is that you might want to "use the official release build". Release builds are made from the same branch as the snapshots, and there is no major special testing befire tagging, so the reason is rather weak in reality. Sure, possible major bugs in a release are probably fixed more quickly than bugs at any random moment.
Otherwise the release branch head, the 22.03-SNAPSHOT on auc terms, contains fixes made after the release and is likely better than the release. E.g. right now, the 22.03 already contains firewall4 fixes and mt7622 uboot pstore fixes that have been backported from master after the rc1 tagging.
Personally I always make my own builds from the branch HEADs.
1 Like
Ah, so it sounds like I have been mistaken in supposing rcX is in theory more stable than branch head snapshots? If so, I'll revert to the latter.
Usually there is not much difference. Rarely the backports contain bugs that are discover later, but that may also happen before a release. (Like said, major bugs in a release may get more rapid attention than the same bug at a random moment.)
But there is nothing major/special in the release tags regarding stability.
Of course, if you are running a production environment, you likely would not upgrade all routers to the random build at the same time, but would see if the build causes any problems in one of them. But the same applies also for releases...
It pays to look at the core OpenWrt source changes. E.g. right now there just a few mt7622 fixes (touching also RT3200), firewall4 fixes (firewall4, ucode) plus iwinfo changes. Nothing major to either direction. Likely no major risks, but quite possibly fixes for the rather new firewall4.
Thanks a lot for your helpful explanations. I struggle to understand the above.
Do you mean that when there is a release candidate, and that release candidate is found to have bugs, there tends to be a more rapid resolving of those bugs than otherwise? If so, I presume that would point towards using the branch head in which such bugs have been resolved?
Not really the release candidates, but the later actual releases, 22.03.0, 22.03.1 etc.
If major bugs would be found in a release, a new point release would be made more quickly.
The branch head likely contains more fixes than the old fixed release did, but on the other hand it may also contain new bugs. That is the drawback.
But release candidates, like the current rc1, are still just test builds in any case.
OK thanks, but is it fair to say at least that branch head is more stable than master head? So maybe a good compromise?
Sure, a release branch is expected to be more stable than the bleeding edge development master branch.
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.