https://www.kernel.org/category/releases.html
The party in Hamburg decided that releases were every six months, so some would be on non-LTS kernels.
But then, 2020.01 is coming up fast and a branch hasn’t been cut yet. Nor have PRs been reviewed on a timely basis. The current thread on PRs on the mailing list has been all about hiding the symptoms, not addressing the problems. Worse is that it is a fox guarding the henhouse situation.
for those wondering, this was written down in the wiki, in an unaccessible page afaik. https://openwrt.org/meetings/hamburg2019/start
That said, it seems most of that is fictional, the core team does not move fast enough to deal with all that in this decade.
?
That page has no access restrictions at all, everybody can read, even anonymous users.
Edit:...and can easily be found via the wiki search.
yeah, if someone knows that they had a meeting and that someone has written down the meeting somewhere in the wiki first, aka someone that most likely does not even need that as is following the mailing list. There is no backlink to it from the main page nor mention elsewhere.
You already know what I think about the searching, if it was so good we would have no structure and just a search box in a blank page.
v19.07.0-rc1 has appeared today, it would seem. So hopefully the release won't be too far off now
19.07.0-rc1 has been tagged a few minutes ago:
buildbot will likely build the rc1 images hopefully in 2-3 days, and then the rc1 will be formally announced.
The speed of the build phase will depend on the amount of buildslaves grandted for 19.07 and currently there is only one active slave, so the omage build could take some time...
The final 19.07.0 release will then depend on the possible bugs/feedback from the wider 19.07 user testing. And possibly there could also the rc2 and/or rc3...
(So far the testing has only been done with enthusiasts, as there have been no public rc builds.)
Exciting times!
Looks like WPA3 hostapd 2.9 won't be in it (I doubt it will be backported between RCs).
What makes you say this? I've been using WPA3 for months on the 19.07 branch.
And there's a wpa3 related commit in the last 25 hours.
I should have said hostapd 2.9, my bad. That probably provides WPA3 security fixes then, if WPA3 is already fully supported in 19.07.
I think we might be covered there too unless you can tell me one of the CVE numbers? I think I recall Jow saying that backporting wpa3 fixes was on the list of 19.07 to do.
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=57ab9e3add0f10795b7db5b1f3d1b2eb9b8f92c9
On the mailing list on October 22nd there was this posted:
- Blocker: All relevant sub-components for WPA-3 + GUI support, such as
hostapd, iwinfo etc. need to be backported to 19.07
Time estimate: 2 weeks
To which Hauke responded:
ynezz has a branch here and I am fine with also backporting hostapd from
master to 19.07, the security fixes are already in.
https://git.openwrt.org/?p=openwrt/staging/ynezz.git;a=shortlog;h=refs/heads/upstream/19.07/hostapd-backports
That tree contains a fix for CVE-2019-11555 (I haven't checked further CVEs).
Edit: nevermind, that patch is already part of the 19.07 branch.
Appeared and disappeared 
Huh?
commit 88bff692a5 (tag: v19.07.0-rc1)
Author: Jo-Philipp Wich <redacted>
Date: Wed Nov 6 09:08:44 2019 +0100
OpenWrt v19.07.0-rc1: adjust config defaults
openwrt https://git.openwrt.org/openwrt/openwrt.git (fetch)
openwrt https://git.openwrt.org/openwrt/openwrt.git (push)
I should've been clearer. It's tagged in git, the release candidate builds are not yet there (which is what you are looking for I expect)
(https://github.com/openwrt/openwrt/tree/112df2ac56f0501d585b8dd414a4e22b38a366f9)/ 112df2a
OpenWrt v19.07.0-rc1: revert to branch defaults
That just means that the 19.07 branch itself has been normalised again after the temporary changes for the 19.07.0-rc1 tagged commit. Quite normal.
(earlier example from 18.06... https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=b84f761d91646520d46abcfbdc79b64079a87f60 )
rc1 was tagged and buildbot is crunching rc1 builds (slowly)
The alternative would be that the tagged releases (and RCs) weren't part of the linear history. This has disadvantages, like "git describe" not working as expected and not being able to do a ff pull from one release to the next. Personally I prefer the rollback commits with one nice history from release to release.
That was done with the earliest 17.01 releases (17.01.0 and 17.01.1) and was noticed to be problematic like you describe, and so the practice was modified to be this rollback commit style where all releases are visible in the linear commit history of the branch.
There are RC1 builds available, just not for most targets yet. It's going to take time for the buildbot to compile them all.