Hey - we're currently starting new web projects designed to go into production this fall. Would you consider Umbraco 14 being ready for production purposes? Or is it still too unstable for this? Our concern is that if go with Umbraco 13, we will encounter an unnecessary tecnical investment of time when we upgrade to Umbraco v14.x or v15, especially upgrading the custom properties we intend to build. Furthermore, we're not strong with Angular and thus building custom properties in Umbraco 14 should be easier and more in line with our strengths. Still - all this considered, I'm still not sure that v14 is stable is enough for production. What are your thoughts?

I think this is a very hard question, and the answer is a very big "it depends". I don't think v14 is production ready for big sites yet, personally, but depending on the timeframe of the project, it is possible I would feel comfortable picking it, if the consideration is exactly about not accruing too much technical debt (ie. write all integrations in angular and then in webcomponents later)

Yeah, this is the classic conundrum when starting new projects so close to major upgrades. I remember we had a lot of challenges when we, after a lot of considerations, started a new Umbraco 8 project back in May 2019.

It's a rough one this time as well. If you are planning on a lot of backoffice integrations I'd probably aim for v14.somethingmorethan-1 and hope, if you are more dependant on "established" packages, that presumably will have a upgrade-path, v13 feels a lot safer right now

Personally no, I would stick with 13, there are still too many things that don't work in 14

Also, 13 is current LTS with EoL December 2026, so you won't need to consider migrating until then.

Also 13 for now.. there are alot of changes in 14, and not everything that is in 13, is ready/avilable in 14

Can I ask, what kinds of "custom properties" are expecting to need to make?

Adding to Jason's question, how long do you expect to be in development? I'd argue 14 is stable but missing bits for your editors, if your actively supporting the site then updates will mean those issues get resolved

Genuinely love that positivity @Matt Wise

Except the core parts that need to work, make sure all **non-core **functionality works in 14 to be able to make a decision. For us, this usually means * Azure storage provider * Azure load-balanced hosting * Forms and custom workflows * uSync * Translation Manager with specific providers * GodMode 🙂 You may have other non-core stuff (third-party or first-party) that you need. Not just full-fledged packages but minor stuff like Examine customizations etc.