Skip to content

feat(devmanual): clean up the new release notes#14574

Merged
ChristophWurst merged 1 commit intomasterfrom
feat/devmanual/release-notes-cleanup
Apr 24, 2026
Merged

feat(devmanual): clean up the new release notes#14574
ChristophWurst merged 1 commit intomasterfrom
feat/devmanual/release-notes-cleanup

Conversation

@ChristophWurst
Copy link
Copy Markdown
Member

@ChristophWurst ChristophWurst commented Apr 24, 2026

☑️ Resolves

Follow-up to #14183 and #14565

This brings the Release notes into the final structure I had in mind with #14180

  • There is one very prominent entrypoint for changes in this release
  • There is one dedicated page for critical changes.
    • These have to be addressed. It's cleared after branch-off because afterwards it is no longer relevant.
  • There is one dedicated page for new APIS.
    • These are nice-to-have for devs, nothing terrible happens if that page is not read.
    • The APIs will have their main documentation on a persistent page. This is just an overview here.
    • It's cleared after branch-off because afterwards it is no longer relevant.
  • There is one collecting page for deprecations.
    • These are nice-to-have for devs, nothing terrible happens if that page is not read.
    • They stay there as long as they are relevant, so until they are removed.

The old upgrade guides stay for now and will phase out. Maybe we hand-pick the deprecations and move them to the new file. I'm too lazy for that right now.
There is a redirect rule to send anyone from the 34 page to the new pages.

🖼️ Screenshots

Entry point Critical New Deprecated Legacy
Screenshot 2026-04-24 at 13-47-10 Release notes — Nextcloud latest Developer Manual latest documentation Screenshot 2026-04-24 at 13-47-19 Critical changes — Nextcloud latest Developer Manual latest documentation Screenshot 2026-04-24 at 13-47-29 New in this release — Nextcloud latest Developer Manual latest documentation Screenshot 2026-04-24 at 13-47-36 Deprecations — Nextcloud latest Developer Manual latest documentation Screenshot 2026-04-24 at 13-47-53 App upgrade guide — Nextcloud latest Developer Manual latest documentation

Signed-off-by: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
Comment thread developer_manual/conf.py
# Removed 2025-04
"basics/front-end/l10n": "../translations.html",
# Moved 2026-04 - Upgrade to 34 moved to release notes
"app_publishing_maintenance/app_upgrade_guide/upgrade_to_34": "../../release_notes/critical_changes.html",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

should not forget to remove this after branch off? :P

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It wouldn't do any harm, right? But yes can be removed at some point

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The single purpose of this redirect is for someone who has already visited https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_34.html to get sent to the new pages instead of a 404.

Copy link
Copy Markdown
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

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

Sure! 👍

@ChristophWurst ChristophWurst merged commit d9135a7 into master Apr 24, 2026
21 checks passed
@ChristophWurst ChristophWurst deleted the feat/devmanual/release-notes-cleanup branch April 24, 2026 13:07
@susnux
Copy link
Copy Markdown
Contributor

susnux commented Apr 27, 2026

Nice but I think this is a bit confusing to have another section split across the documentation.
Why not move all old notes to this new section as well like:

  • Release notes
    • Critical changes
    • New in this version
    • Deprecations
    • Previous notes

We can still make the old links work with the redirects we already have in place for SEO.

@ChristophWurst
Copy link
Copy Markdown
Member Author

Sounds good to move them to this place and add redirects 👍

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.

4 participants