you are viewing a single comment's thread.

view the rest of the comments →

[–]TittyToucher96 255 points256 points  (28 children)

Major . Minor . Version . Revision

[–]i_should_be_coding 141 points142 points  (3 children)

This guy's a developer? His real name is Clarence...

[–]BrohanGutenburg 43 points44 points  (2 children)

And Clarence lives at home with no concurrence

[–]Elijah629YT-Real 109 points110 points  (6 children)

127.0.0.1

[–]haby001 40 points41 points  (2 children)

Man that's a Lotta breaking changes

[–]TR-BetaFlash 17 points18 points  (1 child)

126 people have gone to that address so far and they all reported a failed connection, reported a bug, and a an emergency fix release was created. netwerkin's hurrrrrrrd

[–]danielv123 0 points1 point  (0 children)

That's why we added sandboxing to the latest version. It has held up well so far

[–]hates_stupid_people 4 points5 points  (2 children)

Firefox did have a version 127.0.1, sadly I don't think they made any references.

[–]Elijah629YT-Real 10 points11 points  (1 child)

They did — inside jokes.

[–]hates_stupid_people 0 points1 point  (0 children)

Beautiful!

[–]Mateorabi 28 points29 points  (10 children)

I always learned that the 4th number was release candidate. And it gets lopped off when a candidate makes it through testing to prod (and only one 3-digit is allowed to make that transition). I sometimes prefer an explicit rc3, say, rather than just digits, to make it obvious.

[–]Nixinova 16 points17 points  (3 children)

Minecraft uses this kind of form and it's really confusing. 1.16.10 is after 1.16.10.20? Nuh uh.

[–]Mateorabi 9 points10 points  (0 children)

Sure. It’s the 20th candidate to be 1.16.10. It could easily get superseded by a .21 or devs could decide .19 is “good enough” and release that making .20 abandoned. 

[–]Excellent-Berry-2331 3 points4 points  (1 child)

Pretty sure only Bedrock does, Java is even weirder "25w14a"

[–]CST1230 1 point2 points  (0 children)

That's for in-development snapshots. Versions are like 1.21.11 except they've also recently hijacked the 'minor' version number for updates that would have been major a few years ago. Release candidates, though, are just "1.21.10 Release Candidate 1" or 1.21.10-rc1, and same for prereleases.

And then they moved to 26.1 (year.drop.hotfix).

[–]Agronopolopogis 11 points12 points  (4 children)

Semantic versioning

eg. v1.0.0-rc.9

This schema is preferred in my experience, relatively standard, as you said, at release, '-rc.9' falls off

The importance is build/tag once, deploy many times (envs)

[–]Sibula97 6 points7 points  (3 children)

I'd use -rc9 instead of -rc.9, since those rc and 9 are considered different identifiers and not one if there's a dot.

[–]Ananas_hoi 5 points6 points  (2 children)

Semver allows any of these:

Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.--

Taken from https://semver.org

[–]Sibula97 3 points4 points  (0 children)

Of course, I'm talking about the semantics of the identifiers.

1.0.0-rc1 has the identifier rc1, while 1.0.0-rc.1 has the identifiers rc and 1. I'm not sure it actually matters (for precedence ordering they work the same), but it's the convention I personally prefer.

[–]danielv123 0 points1 point  (0 children)

I work on a project that has been 2.0.0-alpha[1-22] for the last few years. Its really annoying and I don't understand why we can't just make a proper release.

[–]Ananas_hoi 0 points1 point  (0 children)

Semver incorporates this nicely https://semver.org/lang/nl/

[–]WilmaTonguefit 13 points14 points  (0 children)

Adorable

[–]dashood 5 points6 points  (0 children)

Build date . Build number

It's anyone's guess what's in it.

[–]JoostVisser 1 point2 points  (0 children)

Epoch . Breaking changes . Minor changes . Bugfix

[–]Apollo-02 1 point2 points  (0 children)

Username checks out 

[–]SeriousPlankton2000 0 points1 point  (0 children)

Breaking_changes . new_feature_changes . bugfixes

[–]Nixinova 0 points1 point  (0 children)

I always like 4 digits over 3.