Never mind v7.
6.49 has been in the oven now for what, over half a year?
And yes, I know it will be 'When it's ready!'. But roughly when will that be?
No offense, but this seems more like your opinion than what is realistically going to happen. Correction, it seems more like what you would do, less than what Mikrotik would(usually) do.The only sensible reason for releasing 6.49 would be to make it kind of transitional package to upgrade to 7.1. Which likely means including some updated routerboot firmware (so that v7.1 successfully boots) or some configuration sanitizing. Otherwise I don't see any point in doing it. For security releases for devices not being able to upgrade to 7.1 (or for admins that don't want to jump the 7.1 wagon for another year or three), maintaining 6.48 series should do.
I did not mean that they should just switch the current beta build to stable. Ofc. they should fix that bug.Sorry, backup is broken in 6.49beta. THAT IS A BIG THING!!!
v7 Is for me a thing I can't try without BIG risks because I can't go back v6 without having to take a troublesome road of manually restoring the export.
If you can't get out of it, then you shouldn't have gone in to it in the first place. If it's that important, why are you running beta software on it?If 6.49 is declared a dead-end I am in trouble, because I can't go back to 6.48 due to no working backup available in 6.49 and not forward to v7 because the config coversion is not on the radar.
If Mikrotik had not broken backup there would not be any problems. I have lots of experience with running Beta's by Mikrotik and it worked that well that nobody noticed that Backup was broken for several months. I noticed it when I had a short stay on v7 and normally I can return to the Beta without an hitch.If you can't get out of it, then you shouldn't have gone in to it in the first place. If it's that important, why are you running beta software on it?If 6.49 is declared a dead-end I am in trouble, because I can't go back to 6.48 due to no working backup available in 6.49 and not forward to v7 because the config coversion is not on the radar.
You'll just have to Netinstall it and restore your 6.48 backup, and then teach yourself not to be so daft for the next time.
If Mikrotik would me let escape the messed up Beta.Hmmm .. you can't downgrade from 6.49betaX to 6.48.4 without netinstalling device? And you can't get (at least most of) config exported to text file? If answer to both is NO, then I'm surprised.
Don't get me wrong, I didn't say that 6.49 is a dead-end, only MT can declare such thing. I was just saying that this is not impossible. But if that actually happens, I guess you'll have to bite a bullet and get out of this beta mess.
If Mikrotik would me let escape the messed up Beta.... you'll have to bite a bullet and get out of this beta mess.