nextcloud / nextcloud/changelog_server

Missing Changelog

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
7
Forks
3
PR merge metrics
No merged PRs in 30d

Description

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • Nextcloud Server is running on 64bit capable CPU, PHP and OS.
  • I agree to follow Nextcloud's Code of Conduct.
Bug description

There's no changelog for the new V26.0.0 release.

Empty file that refers to a website:
Website https://nextcloud.com
"Blog Post" https://nextcloud.com/blog/hub-4-pioneers-ethical-ai-integration-for-a-more-productive-and-collaborative-future/
  • does not reference "NextCloud 26" nor "V26" or even "26". (again, maybe hub 4 == v26?)
  • does not reference nor link a changelog of any kind. The post could be considered a changelog but is missing a reference to 'breaking', as in "breaking changes".
Comparing GH releases results in 3000+ file diffs. https://github.com/nextcloud/server/compare/v25.0.4...v26.0.0

Please advise where to find upgrade info for admins and an explanation of NextCloud versioning terminology.

Steps to reproduce

see above

Expected behavior

see above

Installation method

Official All-in-One appliance

Operating system

Debian/Ubuntu

PHP engine version

PHP 7.3

Web server

Apache (supported)

Database engine version

MySQL

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 22.2.3 to 22.2.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report
NA
List of activated Apps
NA
Nextcloud Signing status
NA
Nextcloud Logs
NA
Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the empty CHANGELOG.md reference, the nextcloud.com/changelog page, and the linked release-notes page. Determine how V26.0.0 and the Hub/version terminology should be represented; done means upgrade information and a summarized changelog are available and clearly linked.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.