Hugo 0.100.0 Released

Announcements
1

This is a good one.

15 Likes
4

Triple digits! Congrats!

5

Ask functional questions somewhere else … this is a meta thread about the release.

6

Congratulations!

I’ll ask the inevitable question so others won’t have to do it: does going to a version 0.1xx scheme have any connection to whether/when Hugo will reach version 1.x territory?

7

Really happy that we go with 0.100 rather than 1.00.

It seams that development till version 1.00 going slowly and than suddenly changes from 1.00 to 100.00 going like crazy… hence good we goes into 0.100

8

No, and I don’t see any “scheme difference”. If you increment an integer at 99, you get … 100.

3 Likes
9

Fair enough. It’s kind of the way macOS went through 10.0 through 10.9 and then, rather than going immediately to v.1x.x, instead did 10.10, then 10.11, and so on until it reached the current yearly incrementing scheme of 1x.x (currently 12.x).

10

Hugo 0.100.0 packages

Brew - Hugo Brew package for macOS and Linux - updated :white_check_mark:
Snap Package - Hugo Snap (Snapcraft) package for Linux

  • traditional release - not yet updated :x:
  • extended release - not yet updated :x:

Docker/CI Image - Hugo Docker image for Continuous Integration - updated :white_check_mark:
Docker Image - klakegg/hugo - Other Hugo Docker image - not yet updated :x:
Debian (sid) - not yet updated :x: (Track link)
Ubuntu (jammy) - not yet updated :x: (Track link )
Fedora Copr - Hugo RPM package for Fedora and CentOS - not yet updated :x:
Chocolatey Package - Hugo Chocolatey package for Windows

3 Likes
11

I like that you compare the Hugo project with Apple, but we’re a little bit smaller…

The one thing we signal by not going 1.x is that we’re kind of not “1.0 feature complete”. People tend to think a major version would get a more stable version, which I’m not sure is always the case. I suspect you end up with major version increments and, due to lack of human resources, not so much backports of bugfixes to the previous version(s).

4 Likes
12

Brew - Hugo Brew package for macOS and Linux - updated :white_check_mark:

3 Likes
13

When I worked on removing some old outdated posts on my website I noticed that I wrote in the past about Firefox version 3.5.

From my observation, after passing 1.00 “some” developers seams to skip quickly between versions… that suddenly, after a short period of time we dealing with a three-digit version.

I hope that guys from 11ty will not go this route :slight_smile: From 0.1.0 (Dec-17) to 0.12.1 (Mar-21), and now 1.0…

14

Curious, what do you mean by 3-digit version? 100.0.0 or 1.100.0?

15

I am more referring to the abnormal quick jumping from the full number of versions in some software development after going into 1.0 version.

Hugo going quite linear compared to this - Safari versions to Chrome for example.

Some software, let’s say, are year ago 0.14, today 0.18, next week 1.0, you will forget about them for couple months and suddenly they are not in 1.02 but like version 47.0 etc.

ps.

I like that you compare the Hugo project with Apple, but we’re a little bit smaller…

If we looking at version changes in Apple software, Hugo is a good compare :grin:

1 Like
16

For Apple there is obviously also a vanity and marketing aspect to it, too. OS X 12 has a better ring to it than OSX v1.2.0.

2 Likes
17

Love to see Blackfriday ripped out. My favorite part of coding is getting to remove the cruft.

6 Likes
18

Not to derail or anything … in World of Warcraft they quietly used their versions as a way to internally mark expansions.

  • Closed beta: 0.xx
  • Release (original game): 1.1.0
  • 1st Expansion (release day): 2.0.1
  • 2nd Expansion (release day): 3.0.2
  • 3rd Expansion (release day): 4.0.3
  • 4th Expansion (release day): 5.0.4

After that 4th expansion they stopped doing it. Maybe because players were arguing about it endlessly (vanity vs coincidence) in the forums (gaining hundreds of replies; if closed, someone will open a new one); or there was a change in the lead dev.

SemVer is a good idea but doesn’t mean vanity, marketing, or internal meanings can not be added on top of it.

And one thing is clear, major version is definitely for major versions, vanity or otherwise, I think everyone agrees on that.

1 Like
19

You’re the best.

20

Congratulations! Good job!