Skip to content

Conversation

@AndyButland
Copy link
Contributor

@AndyButland AndyButland commented Apr 23, 2025

Description

Includes the following:

Type of suggestion

  • Typo/grammar fix
  • Updated outdated content
  • New content
  • Updates related to a new version
  • Other

Product & version (if relevant)

Umbraco CMS 16.0.0-rc

Deadline (if relevant)

We should publish this when the RC is released. For now, keeping in draft.

@sofietoft
Copy link
Contributor

Hi @AndyButland !

Will this include all Docs updates for Umbraco 16?

Also, the 16 docs is not published yet, and won't be until we publish the RC docs.
So, this can easily be merged before, as it will only be available here on GitHub until the RC release.

@AndyButland
Copy link
Contributor Author

I've suggested to the team they can add small things here - little updates as and where needed, like the one I've added. Though likely anything more substantial will have their own PRs to make them easier to review.

@sofietoft
Copy link
Contributor

Great! I see we have a meeting tomorrow, so we should coordinate who writes what - just so we don't accidentally do double-work.

Copy link
Contributor

@sofietoft sofietoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is still in draft mode, but since the RC is going on tomorrow, I thought it made sense to start the review 😅

In addition, I have a question:
Should we remove the breaking changes for the previous versions?
Or perhaps only keep the supported versions there? 🤔 So, that would be 10, 13 and 15 in this case..
This goes for both breaking changes and version specific upgrade notes.

@AndyButland AndyButland marked this pull request as ready for review April 29, 2025 11:01
Co-authored-by: sofietoft <stk@umbraco.com>
@AndyButland
Copy link
Contributor Author

Good point @sofietoft! Thanks, and sorry for forgetting to mark this as ready for review.

On the breaking changes point, I think it's probably best to keep in actually. Just as if you are going from say 13 to 16, it makes sense you read the breaking changes between 13 to 14 and 14 to 15, even if you are upgrading in one step. You could go and find the 14 and 15 docs to see these, but it's an extra step and it may not be obvious that you should review them.

@sofietoft
Copy link
Contributor

Yes, good points about the breaking changes docs 🤔
We could remove the RC and Beta ones for 14 though, right?
image

And perhaps 12 and 11, as they are no longer supported, so you wouldn't be updated to those - and I don't believe you even need to, in order to go from 10 to 13 🤔

@AndyButland
Copy link
Contributor Author

The beta and RC ones could go for non-current versions I'm sure.

But for this...

And perhaps 12 and 11, as they are no longer supported, so you wouldn't be updated to those - and I don't believe you even need to, in order to go from 10 to 13

... I think we should keep. You are right that you don't need to do the intermediate upgrade steps - i.e. you can upgrade 10 to 13 - but you still might want to know what all the breaking changes are between the versions you are going between.

@sofietoft
Copy link
Contributor

Yes, you are right. The breaking changes remain relevant, so we'll keep them 😄
Just thought it'd be a good opportunity to clean up a bit.

I'll merge this, and make sure the RC docs are published tomorrow.

@sofietoft sofietoft merged commit f6eb872 into main Apr 29, 2025
15 of 18 checks passed
@AndyButland AndyButland deleted the cms/16-rc branch May 6, 2025 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants