@gameboy What a rude way to welcome me back from my holidays ...
Whether you hate me or not ... well ... let it be !
As the forum states on the 1st page: we're working on pi3b+! You may not believe it, but in real, this is ready since ... May, or maybe june I'd say, but only for the recalbox team. But as it's been explained numerous times, there were a few prerequisites:
new upgrade procedure: this one too is ready for a long time. But as this is EXTREMLY critical, it has to be throuroughly tested, I'll talk again about this point later, and it must go along with the next point
new infra structure deployment to make sure people won't make a "too big" upgrade that will break their Recalbox. This is ready since June too
gather all this, prepare the upgrades, beta tests, deployments, upgrade URL for public testing: this could have been done before my holidays, but what's the point of starting an open beta if I can't manage bug reports because I'm on holidays ?
You've probably noticed there were 2 releases for the last month, which of course had an impact on the timetable for the open beta we were hoping to start sooner. Well, that's part of the game, we had to make a quick fix release, we (in that case it was solely me) make errors sometimes.
The open beta with pi3b+ should start in the coming days I hope (less than a week for sure, depends on the time I have).
Now regarding the overall tone of your last posts ... it's not this way you will get people's sympathy, nor will you motivate the Recalbox team to keep spending countless hours every week. We get tens of messages everyday asking us to be pi3b+ compatible. Even 2h after the pi3b+ release, some people were already asking us if Recalbox was compatible (whereas even raspbian WAS NOT yet compatible) ... Jesus Christ ... People's impatience and ungratefulness' only limit is becoming even bigger than the universe itself ...
Now you're a grown up, you make your decisions, you can do whatever you wish on your pi3(b+), you can hate me as much as you want (do I assume correctly that you're the one who opened the issue on gitlab?). Butthis is in no way a reason to tolerate your behaviour on this forum, so please mind your language, once for all.
