nextcloud / nextcloud/server

Please fix the versioning scheme of Nextcloud Hub

Open
#64,474 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

[!TIP]

Help move this idea forward
  • Use the 👍 reaction to show support for this feature.
  • Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
  • Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

I am always confused when I see the version in my nextcloud instance. It says: "Nextcloud Hub 26 Spring (34.0.3)", and I think "wait, it's been summer for months, did I miss an important update?".
Same effect when I see an announcement like "Nextcloud Hub 26 Summer is here". And I think "but it's autumn, why is the 'summer' version released in autumn?".

I know that astronomical autumn only starts in a week or so, but per the meterological seasons September is already part of Autumn. So I find this naming ambiguous and confusing.

It is also confusing to see a version list like this:
Nextcloud Hub 26 Winter (version 33.0.7)
Nextcloud Hub 26 Spring (version 34.0.2)

Winter coming before Spring?
I know that technically the year starts in Winter, but I would argue the common sequence for most people is spring, summer, autumn, winter.
But be that as it may, how do you explain this naming scheme to people living south of the equator?

Describe the solution you'd like

Just call it Nextcloud Hub 33, Nextcloud Hub 34, Nextcloud Hub 35, and so on.
I don't think it really matters in which year or season it was released.
If the year is so important use quarters (Q1, Q2, etc.) instead of seasons. At least this way the sequence is unambiguous and does not require me to re-calculate in my head that "summer" means "almost autumn".

Describe alternatives you've considered

Additional context

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

The issue names no files, tests, or entry points; begin by locating where Nextcloud Hub versions are defined, displayed, and announced. Done means replacing the seasonal naming scheme with an unambiguous numbering or quarter-based scheme consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.