May I ask what this means?
Developers are attempting to incorporate a generic driver model that fits "every" graphics engine, meaning we want to steer away from having to fix & develop separate builds for every type of Android box that has a divergent chipset. Looking at you, AMlogic...
Right now 99% of RPi efforts have gone into the 4B. Sadly we cannot copy/paste most of that work back onto the RPi3.
Is it the end for the rpi3?
If I got informed correctly, currently the RPi3 builds do not support HEVC/H265, which is increasingly favored by users for obvious reasons. There are nightly builds with Kodi 19 around, but they will have their bugs.
One other thing: the TVDB APIs v1-3 will be taken offline in a few months, and the new v4 api will get enabled. For now, there will only be support for TVDB v4 in Kodi Matrix and upwards. So, scraping with TVDB in Kodi 18 and lower with RPi3B devices will stop.
However... Kodi already switched to TMDB for both movies and tv shows. So there is an alternative for that.