Just wanna complain a little bit.. still seeing so much bugs in latest Umbraco 16 today.. We choose for Umbraco 16, te release new website in november, so we could later upgrade to 17 and our customer would have the latest shiny version of Umbraco. But when working with it on daily base, we truly regret our decisission and we truly ask ourselves if we should downgrade the entire codebase to Umbraco 13, because Umbraco 16 doesn't even seem to be a alpha version of a good product. 🙁

I'm curious what issues you are running into. Yes some small quality of life things are missing, but I'm actually pretty happy with Umbraco 15 and 16.

a lot of waiting, properties seem to be appearing late after page refresh, all of a sudden 404 errors, no feedback after sorting, very late feedback after publishing, copy/paste of blocklists is terrible, listview settings don't do anything etc etc

Hmm I haven't had issues with that so far to be honest

Running with the latest build is always going to be a rocky ride. Things are changing, and documentation is very limited. You could downgrade to v13 for stability, and probably wise if you are only using core functionality, as the upgrade back to v17 should be seamless - This is strategy I use for my own sites.

It depends if you extend the backoffice. But if you have just Umbraco and you're not using nested content and macro's, the upgrade shouldn't be that hard

Yeah, Razor and Views and Controllers should behave the same. There's some small changes in Culture/Languages - but if you're not using localization, then you are safe.

And if you have UmbracoAuthorizedApiControllers, you need to change them a little to the management API

the most annoying this is when I'm using my site locally, when I open a node, I see just a part of the properties.. In the beginning it scared me: what happened to my precious properties.. Now I now I sometimes have to wait for 20 secs for them to appear on the screen.. Also the content tree sometimes appears empty.. In both cases I don't see any loader or load activity, so it's very confusing in my opinion.

Hi Remko, we have experienced some similar things and our decision to go for 16 was the same as yours. Completely understand the difficulty in rearchitecting everything in the CMS interface but hitting a lot of niggles and gremlins especially on a large website.

Might be worth creating an issue on the Github with your experiences? You might have ran into things that aren't on the radar of the team yet

Can't imagine this list of basic functionality isn't on the radar yet.. with just a little bit of clicking you'd see it all happening

I agree that some things can have a bit more polishing, but I have to admit that I do not share your experience with things being slow.