No worries on that, this is all openSUSE managed. We no longer have any part in kernel versions or btrfs-progs versions. And they make the decisions on the exact version numbers. Plus if you look up the major kernel version it also is relatively old, but that doesn’t take into account the back-ports. What you could do it look to the Changelog for each package and see what they (openSUSE) have back-ported to these major version numbers. They cherry pick stuff you see as the bleeding edge is not always the best to use. And given openSUSE/SUSE employ a good number of btrfs devs they are in a good position to identify what is less risky to backport. And is is often the case that there are teething problems with major version updates so they hold off on them. For an example of the discrepency between major package version number release date and back-port dates see @Flox’s post here:
Where you see that in a Leap 15.1 4.12 kernel there was a one month old btrfs back-port. Yet 4.12 (the major version) was released in 2017. So distribution packages often stick to older major versions and cherry pick patches, often hundreds of them. Hence our discioion to go this openSUSE who are, as mentioned, well placed to make these decisions.
Yes we look to have an email issue on that one and I have started a fresh email thread to resolve this. I’m also going to PM you in the forum to help resolve what’s going on there as I have you original activation email as having been delivered and have also copied it into a thread we have ongoing in support so all a bit strange but we will get it sorted one way or another. Likely just a quoted email that was hidden as required a click to expand or the like. I’ll copy into the PM what I’ve also just sent you re the activation code which itself was a copy of what was sent on 8th August. But at least we also have the forum.
Hope that helps.