@northlight wrote earlier:

...

I have 7.2.2 and a 7.3 running and now I am wondering

Heck, I was not even aware that b2evolution '7.3' was available!

@northlight wrote earlier:

if it is possible to downgrade a 7.2.2 to the latest stable 6.11.x version.
Did anyone try that already?

As long as you made a dump(s) of your MariaDB/MySQL database(s) prior to upgrading to version 7.x.y and created a backup archive of your b2evolution 6.11.x PHP application code -- especially your media content / skin(s) customization) -- downgrading is usually straightforward.

Create backups prior to deleting components It is always best to be on the safe side.
Delete the 7.x.y created database(s) as well as the corresponding PHP application code tree version. Then restore your 6.11.x MariaDB/MySQL db dump(s) as well as the backup archive(s) of your b2evolution 6.11.x PHP application code tree -- (and again) especially your media content / skin(s) customization).

The specific steps required vary depending on the GUI tools you are using and/or the shell (i.e., bash, zsh, etc.) commands utilized from the server side.

But yes, it can be accomplished -- as I have done it on a couple of occasions in the past --for the same buggyfull reasons as you elaborated. Note, as well, that any new content you created after the upgrade needs to be recreated in the restored components since -- for instance -- the DB schema before the upgrade is different from that of the upgraded DB.

@northlight wrote earlier:

Why?
Because there are too many challenges with 7.x and since weeks no action wa/is taken in the 7.x branch: https://github.com/b2evolution/b2evolution/tree/7.3dev

I agree. It's been quiet on the github side, i.e., no commit notices, etc., etc.. It is always good 'not to place all eggs on one basket' in case this project becomes orphaned. Hopefully not, of course!

P.S. Please note that there are also occasions when competing CMS are released without being well tested, apparently. I have had to deal with at least one case with that CMS which name starts with a 'D' ;-)

@nanahuatl wrote earlier:

Heck, I was not even aware that b2evolution '7.3' was available!

Isn't "tested" but somehow working.

B2E is so pre-loaded that it is understandable that not all functions can be tested before publishing.
But it would be appreciated it bugs would get fixed, once the devs have heard about them.

@nanahuatl wrote earlier:

As long as you made a dump(s)

Thanks - sometimes you don't see the forest....

@nanahuatl wrote earlier:

I agree. It's been quiet on the github side, i.e., no commit notices, etc., etc.. It is always good 'not to place all eggs on one basket' in case this project becomes orphaned. Hopefully not, of course!

I am struggling with B2E ever since.
I play with them (different releases) locally and I am overwhelmed about the functionality.
But
in my eyes, the B2E logic is more complicated and time consuming than TYPO3 with its own config language. ( And -> TYPO3 is no Blog ;) )
And in this forum, the response time and quality of answers is not always exemplarily.

@northlight wrote earlier:

And in this forum, the response time and quality of answers is not always exemplarily.

Peer to peer help is always only going to be as good as the user's skill and time available, so to be exemplary is a wish to far:)