> On Sep 22, 2018, at 4:42 PM, Hauke Mehrtens <ha...@hauke-m.de> wrote:
> Signed PGP part
> Hi,
> We talked about plans for the next OpenWrt releases in this mail thread:
> http://lists.infradead.org/pipermail/openwrt-adm/2018-July/000849.html
> This mail is more or less a summary of the conclusions, this is still
> open for change especially the dates as this depends on people having
> time to do the work.
> The next release, lets call it OpenWrt 19.01, should happen in January
> 2019, we would branch off from master in December 2018. This is the
> current plan, but based on past experience it could also happen later.
> OpenWrt 19.01 will ship with kernel 4.14 only, we encourage everyone to
> update the targets to kernel 4.14, support for kernel 4.19 will probably
> be added to OpenWrt master soon, but we will not select it as the
> default kernel for any target till OpenWrt 19.01 is branched off, to get
> more testing on 4.14. The release after 19.01, which should happen in
> late summer 2019, should then use kernel 4.19 only.
> For OpenWrt 19.01 GCC will stay on the 7.X branch, binutils and musl
> already got some upgrades after the 18.06 release and could get some
> more updates.
> We are currently working on updating the wireless drivers and getting
> them closer to upstream. The wireless driver in OpenWrt 19.01 will be
> taken from kernel 4.19 or later and we want to update them more
> frequently in master.
> Otherwise we will have the normal changes in all places like with every
> release.
> LEDE 17.01 will get security updates and occasional bug fixes till
> OpenWrt 19.01 was released, but we encourage everyone to upgrade to
> 18.06 to get full security support already now, as especially some of
> the packages are not well maintained any more.
> Hauke

Hi Hauke,

This reminds me of an issue I’ve run into.  xtables-addons-3.0 will build on 
4.14, but xtables-addons-3.1 requires 4.19 at a minimum.

Is it reasonable to have xtables-addons/Makefile pick a version based on the 
kernel version?


openwrt-devel mailing list

Reply via email to