When comes the next stable release 19.x

For Developers
27

Do they have schedule to release 19.07?

28

Any news on release date?

29

Latest discussion on the mailing list:
https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg48100.html

30

"gradually getting stale" is something of a polite understatement

$ git log --pretty=oneline openwrt/master ^openwrt/openwrt-19.07 | wc -l
741
$ git log --pretty=oneline $(git merge-base openwrt/master openwrt/openwrt-19.07)..openwrt/openwrt-19.07 | wc -l
163
2 Likes
31

19.07 branch is already a release quality. Openwrt developers always struggled to release anything. It was declared to do a release each 6 months, but they can't do one in a year. Nobody of the core developers are interested in releasing anything. They just move master ahead.
I am quite happy with making 19.07 builds.

3 Likes
32

I don't think this one has been fixed yet: Flow_offloading=1 is broken on latest snapshot (4.19 issue)

Since 19.07 includes flow offloading for the first time for a number of popular devices (ath79) I think it's critical to have that fixed before releasing it.

33

As far as I understand default kernel version for 19.07 build version for your device is 4.14 and not 4.19

3 Likes
34

It is broken only on master, not on 19.07.

3 Likes
35

Packages that are updated at source being only committed to Master but rarely to the stale 19.x branch. By the time 19.x gets released those packages will be outdated already and who knows when the next branch after 19.x gets forked off Master - at the current pace probably not for another year.

36
  • Package updates are independent of releases
  • Lack of package backport/cherry pick activity is not entirely the fault of the developers, the majority of package updates happens in the feeds
37

Unless I am miss-comprehending various forum posts I am under the impression that packages should not be updated by the user individually/independently of release updates (sysupgrade)?

You lost me there - I would understand that would apply to packages fed from other repos (feed) than the main OpenWrt. And anything provided by the OpenWrt repo (feeds) needs to be uplifted/backported to the specific branch repo after being tested in Master repo, which does not seem to happen automatically.

There are a number of packages in Master that are on par with source but not making it into the branch. And with the current release pace who knows when Master being forked again?

38

Thorought the lifetime of a release, binary packages of the latest available version in the branch are automatically built and made available in the repositories. There is no release required to get the latest version of some optional package, it just needs to be backported to the branch by its respective maintainer [within certain limits].

Correct, it does not happen automatically and needs to be done by the maintainers of the respective packages. The release branch is forked once initially and used as baseline for the builds. If nobody cares about it or backports stuff into it, it will get stale.

39

And there starts one of the problems, that maintainers are often not interested to backport to the current branch and rather prefer waiting till Master gets forked, which can be quite some time.

But that is perhaps digressing from the thread topic.

40

Exactly, but in my view a release is not a simple unmaintained archived master snapshot just for the sake of getting updated packages. If this is the sole requirement for a release, one could as well use snapshots.

1 Like
41

Maybe maintenancers and developers can share their plans on release dates? I believe they read this forum.

42

19.10 is coming, just saying...

43

What?????? 19.10 release date

44

What month is it

45

november??

46

Next month (October).