Not really: http://forum.mikrotik.com/t/v7-11beta-testing-is-released/167585/1
Don’t waste time on alpha unless explicitly instructed to do so by MT staff.
For me the latest version now is this beta.
Running for almost 11h now on AX3 and A2, so far no more strange log entries seen related to wifi disconnect/disassociated.
Some disconnects yes, but that’s me moving around in the house with my phone in my pocket 
7.11beta2 IKEv2 client does not connect to 7.10 IKEv2 server! Revert to 7.10
Here is ipsec client log:
08:22:53 ipsec ike2 starting for: 777.777.777.777
08:22:53 ipsec adding payload: SA
08:22:53 ipsec,debug => (size 0x30)
08:22:53 ipsec,debug 00000010 00000021 01010001 01000001 01000001 10010100 01000001 01000001
08:22:53 ipsec,debug 01000001 03000001 00000001 01000011
08:22:53 ipsec adding payload: KE
08:22:53 ipsec,debug => (size 0x90)
08:22:53 ipsec,debug 00012320 00151230 000123f1 da6f8cfc c8bdec53 d71232b5 a471238f 98e123a2
08:22:53 ipsec,debug 71dc1233 8212362d 035d1232 488e4e37 c912323d 37123b0c 31765626 9ce1230b
08:22:53 ipsec,debug 0be12344 ba123ab1 4123f93a 0000003b 4f123b45 830e9279 8a3123fc a4122012
08:22:53 ipsec,debug 13a12372 2b1233ea a123aff7 07f4b4e1 46121588 64b371e3 6e123204 80d1a07a
08:22:53 ipsec,debug d2112321 016e1233 4d12315f b3ce21b7
08:22:53 ipsec adding payload: NONCE
08:22:53 ipsec,debug => (size 0x1c)
08:22:53 ipsec,debug 0000001c ec271232 c4f12316 a13123f3 ee1233ba 6913232c c5e1262c
08:22:53 ipsec adding notify: NAT_DETECTION_SOURCE_IP
08:22:53 ipsec,debug => (size 0x1c)
08:22:53 ipsec,debug 0000001c 00012304 451123ef 789123d2 ed12347f 1701234e 8d123049
08:22:53 ipsec adding notify: NAT_DETECTION_DESTINATION_IP
08:22:53 ipsec,debug => (size 0x1c)
08:22:53 ipsec,debug 0000001c 00001235 e2b123d3 c4712af5 fda1232e 2123215dc 43123b4d
08:22:53 ipsec adding notify: IKEV2_FRAGMENTATION_SUPPORTED
08:22:53 ipsec,debug => (size 0x8)
08:22:53 ipsec,debug 00000008 0000402e
08:22:53 ipsec <- ike2 request, exchange: SA_INIT:0 777.777.777.777[4500] a6be46361893bb01:0000000000000000
08:22:53 ipsec,debug ===== sending 312 bytes from 192.168.100.2[4500] to 777.777.777.777[4500]
08:22:53 ipsec,debug 1 times of 316 bytes message will be sent to 777.777.777.777[4500]
08:23:02 ipsec <- ike2 init retransmit request, exchange: SA_INIT:0 777.777.777.777[4500] a6be46361893bb01:0000000000000000
08:23:02 ipsec,debug ===== sending 312 bytes from 192.168.100.2[4500] to 777.777.777.777[4500]
08:23:02 ipsec,debug 1 times of 316 bytes message will be sent to 777.777.777.777[4500]
08:23:07 ipsec <- ike2 init retransmit request, exchange: SA_INIT:0 777.777.777.777[4500] a6be46361893bb01:0000000000000000
08:23:07 ipsec,debug ===== sending 312 bytes from 192.168.100.2[4500] to 777.777.777.777[4500]
08:23:07 ipsec,debug 1 times of 316 bytes message will be sent to 777.777.777.777[4500]
08:23:12 ipsec <- ike2 init retransmit request, exchange: SA_INIT:0 777.777.777.777[4500] a6be46361893bb01:0000000000000000
08:23:12 ipsec,debug ===== sending 312 bytes from 192.168.100.2[4500] to 777.777.777.777[4500]
08:23:12 ipsec,debug 1 times of 316 bytes message will be sent to 777.777.777.777[4500]
08:23:17 ipsec ike2 init timeout request, exchange: SA_INIT:0 777.777.777.777[4500] a6be46361893bb01:0000000000000000
08:23:17 ipsec IPsec-SA expired: ESP/Tunnel 192.168.100.2[500]->777.777.777.777[500]
08:23:17 ipsec acquire for policy: 10.10.1.0/24 <=> 10.10.0.0/24
08:23:17 ipsec policy group mismatch, ignoring.
yes — any chance to ever get a changelog that’s actually informative? especially given this is test release, so users need to understand what’s the expected or corrected behavior?
or I guess we should be thankful for any handouts, as usual, and not make too much noise.
this doesn’t work:
*) lte - added “at-chat” support for Dell DW5821e-eSIM modem;
each AT commands still report “Modem not supported”. Any way to add also telemetry using MBIN on these modules?
I’ve already opened a support case SUP-119507
I was given 7.11 alpha by support for rebooting/link flapping issue on CubeSA 60Pro ac but see nothing relevant in release notes here.
*) w60g - improved stability for Cube 60Pro ac and CubeSA 60Pro ac devices;
The 7.11alpha I was given by support did not fix this one for me.
did not fix what?
Reboots on the AP, ie, did not improve stability.
Did additional testing, consistently low 800 now using TP-Link AX USB device.
Same with 7.8 and 7.10.
Tested today on ax2,3, cap ax, no problems with wifi.
@holvoetn what are you using for testing speed ?
I use openspeedtest locally on on my NAS server but you can install it on raspberry also.
Iperf in container on rb5009.
OVPN works much better!!
I cant make any difference into wifi stability. No link downtime for last 24 hours. Works stable for me. hAP AX3.
For the first time I have on log that WiFi device roamed from WiFi 5ghz to 2Ghz and the opposite. It seems that WiFi roaming is finally working
It worked before as well, it wasn’t just reported in the log 
I can confirm I no longer have the OpenVPN UDP connection issues I had with 7.10, just upgraded from 7.9.2 to 7.11beta2 on my RB3011-iUAS-RM and all OVPN tunnels came up clean and stayed up.
Wifi performance still poor in this build too.. Constantly buffering on smartphones. But think that MKT devs are in good way to push first “stable” build.
hopefully also have been fixed the kernel problems that are present since 7.10 in the ccr ( we have 6 devices with the same probleme since 7.10 )
router was rebooted without proper shutdown, probably kernel failure
kernel failure in previous boot