The name of the next Nextcloud 33 release?

🔮 Meta
,
1

I don’t think the ‘Support’ section is quite right. If it’s wrong, please move it.

I saw at https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule that the next Nextcloud 33.0.0, to be released on 2025-02-28, is to be named

Nextcloud Winter (33.0.0)

I find this a bit impractical, as I cannot 100% define the term Winter as the beginning or end of a year. It may also seem as though far less time has passed between the Autumn release and the Winter release.

This would result in the following, for example:

Nextcloud 32 Autumn
Nextcloud 33 Winter
Nextcloud 34 Autumn
Nextcloud 35 Winter

I know that 2025-02-28 is in the season of Winter and not Spring. But the weather is often quite good at that time of year, and I would also prefer the names and their order:

Nextcloud 32 Autumn
Nextcloud 33 Spring
Nextcloud 34 Autumn
Nextcloud 35 Spring

Perhaps you could reconsider this.

1 Like
2

You missed the ‘Hub 26’ part! It’s 'Hub 26 Winter’, not just ‘Winter’. :slight_smile:

As far as I’m concerned, they might as well omit all the additional names and just stick with the version numbers as they did initially.

However, If they had asked me, I would have suggested using a year/month scheme, perhaps combined with a cloud name, e.g. ‘Nextcloud 26.02 Cumulus’, similar to what Ubuntu or TrueNAS does.

But to be honest, I don’t really care. :wink:

2 Likes
3

Oh sorry. Here my corrections. Not really better:

With Winter:
Nextcloud Hub 25 Autumn (32.x.x)
Nextcloud Hub 26 Winter (33.x.x)
Nextcloud Hub 26 Autumn (34.x.x)
Nextcloud Hub 27 Winter (35.x.x)

26 Winter can be either before or after the 26 Autumn (related to four seasons of a year).

With Spring:
Nextcloud Hub 25 Autumn (32.x.x)
Nextcloud Hub 26 Spring (33.x.x)
Nextcloud Hub 26 Autumn (34.x.x)
Nextcloud Hub 27 Spring (35.x.x)

26 Spring is always before the 26 Autumn (related to four seasons of a year).

1 Like
4

Not really, no. :wink:

EDIT: Although it’s better than the Hub version numbers before, at least the hub number now refers to the year and isn’t just another version number, which was kind of confusing.

I edited my post above as well. But ultimately, I really only wish for a release that’s as bug-free as possible, no matter what it’s called. :wink:

2 Likes
5

I think everybody agrees simple and clear semantic numbering without garbage words like Hub, Winther, Spring, day or night or whatever else would be much clearer and easier.. but for reasons nobody understand Nextcloud chooses the worst possible product name (remember “Nextcloud Teams”? :man_facepalming: good luck on SEO)

6

I’d prefer “Spring” and “Fall” instead of “Autumn”.

7

Well, at least in the northern hemisphere, February is still in winter and not spring, which brings us to the next problem with seasons as names. Just ask someone in Australia what season it is right now :wink:

Oh, and ‘fall’ is mainly used in North America. In the UK and the rest of the English-speaking world, they say ‘autumn’, while in the southern hemisphere it would of course be spring at that time of year. :wink:

8

and there is not just the gregorian calendar :winking_face_with_tongue:

Gregorian: Wednesday, 7 January 2026
Mayan: Long count = 13.0.13.4.5; tzolkin = 11 Chicchan; haab = 3 Muan
French: 18 NivĂ´se an 234 de la RĂŠvolution
Islamic: 18 Rajab 1447
Hebrew: 18 Teveth 5786
Julian: 25 December 2025
ISO: Day 3 of week 2 of 2026
Persian: 18 Dey 1404
Ethiopic: 29 Takhsas 2018
Coptic: 29 Kiyahk 1742
Chinese: Cycle 78, year 42 (Yi-Si), month 11 (Wu-Zi), day 19 (Xin-Si)
Julian day: 2461048
Day of year: Day 7 of 2026; 358 days remaining in the year
Discordian: Boomtime, Chaos 7, Year of Our Lady of Discord 3192

(isotropic.org > today's date)

In Julian calendar it’s Christmas today :christmas_tree:

9

Okay, fair point, I guess. So the simplest and best approach would be to focus solely on the version numbers again and simply leave out all the name fuss. :wink:

However, and I have to be a smartass here again…

Even though there are different calendars, today is January 7, 2026, according to the Gregorian calendar everywhere in the world. This means that even in regions where the Gregorian calendar may not predominant, this date would not be wrong and could be converted to the other calendar, while the seasons are simply always wrong on one side of the globe. :wink:

Oh, and before anyone brings it up, of course, there are also time zones and the International Date Line to consider, which means that it is not the same day everywhere in the world at any given moment. However, with a month/year scheme, this would only be an issue if the release were to take place on the first or last day of the month, and only for a matter of hours. :smiley:

1 Like
10

Hi team,

Sorry for the complexity here!!! I totally get that not everyone loves the naming scheme. And yeah, you can say - marketing is stupid, I’ll give you that. Part of the reason for that is because marketing deals with humans and we’re all strange animals, you know…

We need the version numbers to communicate new versions to press and people who don’t know Nextcloud. That’s important - not directly for all of you, but to get in front of people who don’t yet use Nextcloud helps, indirectly, everyone :wink:

We have a bit of the same challenge as the Linux kernel: when 6.17 comes out, nobody blinks. When it moves to 7.0, there’s quite some coverage. In reality, both are equally big releases, as Linus’ rule famously is: “when I can’t count it on fingers and toes anymore, I go up a major number.”

At Nextcloud, we’re at 32. Going to 33 sounds - like a small step. Version 1.0 to 2.0 sounds MUCH bigger. Of course, the amount of changes going in 33 are far bigger than what we did, per release, back in 2016…

So, we came up with Hub, reset numbering - but that’s also well over 10. Year will scale better, as bb77 pointed out. yup yup. Then how do we differentiate the 3 releases in the year? Ideally it is ordered - random-ish names like Cumulus doesn’t do that. 26.1 and 26.2 is ordered, but sounds like minor releases. We thought - seasons have an order, let’s do that.

Given Hub 26 Spring, Summer and Autumn, you know what’s newer and what is older. Unfortunately Winter is indeed a confusing factor - can be beginning or end in the northern half of our planet. Summer has the same in the south. Mja. Nothing’s perfect I guess :confused: for now we do this.

Of course, you can keep using 33-34 and so on if you prefer, we will have these numbers in the product and on our changelog and download page etc…

2 Likes
11

From a technical perspective, numbers are appealing and allow for clear product naming.
However, can anyone immediately tell me the difference between Windows 5.1 and Windows 6.0?
One was XP, the other was Vista. Now, many can provide details and have memories of the version.

Many successful products have names (Windows versions, macOS versions), and as long as the internal numbers remain, I have no issue with the product names (marketing).

Jm2c.

12

Awwyeah, the man himself, is back on the forums :smiley: Seriously, nice to read you, and looking forward to the presentation of 33/Winter/Hub <lost track of that numbers> :wink:

You never were on phoronix.com, wern’t you :smiley:

I just wanted to smart off a little about the winter/summer thing. To be honest, I find it mostly amusing when people get upset about marketing stuff like that. I think cloud names would be really cool, though, but as I said, I don’t know how quickly you’d have to start over again. But maybe you could put a funny adjective in front of it, like Ubuntu does.

Either way, Nextcloud 33 is coming for us, and it seems to have some not insignificant backend changes. I hate the word “game changer,” but my gut feeling tells me that it’s heading in the right direction. :slight_smile:

13

As a cautious sysadmin, I’ll probably stay on 32 / 2025 Autumn / Broody Bovine for a while (hell, it took me until recently to upgrade to 31 / Hub 10 Spring 2025 / Ambient Axolotl), but I’m curious to hear what these backend changes are for 33 / 2026 WinterPart2 / Calm Coelacanth!

14

as everyone seems to count their small changes here are my 2ct:

I don’t have anything against new namings. But as I read between the lines now NC is trying to re-invent the wheel. But it’s gonna rumble because they use a four-piece base to cover a 3-piece layout. Meaning, apparently they try to get 3 new versions out per year but chosing seasons as part of the names indicates 4 versions. You even can’t abbreviate the seasons as there are 2 s-seasons.
But hey… brandnew idea, we could introduce a sprummer-version - spring&summer. And so we would have 3 versions in a 3-piece namingscheme. Perfect, right?

Anyways… keep it simple guys… please.
Ya, “hub” is a must-have, apparently. But it really doesn’t mean anything, especially not for ppl who don’t use NC up to now (apparently they are focussed with the new namingscheme.) On the other hand you now need that hub-thing to keep to sane namings… since there already has been NC26 etc.

So welcome Nextcloud Hub 26 winter, v33, (released in feb) followed by
Nextcloud Hub 26 summer, v34 (prolly released in jun) aka “sprummer”
Nextcloud Hub 26 autum, v35 (prolly released in sep)
Nextcloud Hub 27 winter, v36 (…) etc

btw - looking at this scheme above it implies a bigger step between NcH26a and NcH27w - with NcH26s and NcH26a being minor steps ahead.

So puuuleeeeeease, Nextcloud, don’t add any further names to it. even if it might be la derniere crie.

15

Yes. In my opinion, this hub suffix would only make sense if there were also a Nextcloud without a hub. :wink:

Okay, to be fair: if you install Nextcloud from scratch and don’t select the “hub” apps in the wizard, you’ll probably only have Nextcloud.

But what if you only install some of these apps? Is it still a hub then? :wink:

Besides, Nextcloud already has “Cloud” in its name. And cloud, as we all know, suggests auto-magic and unlimited possibilities. I mean, could it get any better? Why bring it back down to earth with a simple technical term like “hub”? :wink:

EDIT: Actually, it’s the different numbers for Nextcloud (33) and Hub (26) that make it kind of confusing. If it were just Nextcloud Hub 33 or 26, I don’t think anyone would discuss it at all (unfortunately, the latter isn’t possible anymore).

OK, there’s also the ‘Winter’ suffix, which is what this thread was actually about, but I won’t go into that again. :wink:

1 Like