News for hackers. Stuff that matters.
Re:ZeroVer: 0-Based Versioning by mjburgess on Thursday August 12, 2021 @06:56AM (#28154662)
Seemed like a strange joke until you see the table,

    Project Stars Released Releases        Current Version    0ver years
    React Native 96,747 2015     359         0.65.0-rc.2 (2021)   6.3
...lol

God forbid tor, sklearn, react-native release a v1 -- people might expect things!

Re:ZeroVer: 0-Based Versioning by formerly_proven on Thursday August 12, 2021 @07:08AM (#28154759)
OpenSSL went to double-letter patch versions in their 0.9.x days, for example 0.9.8zh.
Re:ZeroVer: 0-Based Versioning by throw0101a on Thursday August 12, 2021 @08:24AM (#28155336)
> OpenSSL went to double-letter patch versions in their 0.9.x days, for example 0.9.8zh.

They only used single letters:

* https://www.openssl.org/news/changelog.html

The IEEE Ethernet standards are using double letters though:

* https://en.wikipedia.org/wiki/IEEE_802.3

Re:ZeroVer: 0-Based Versioning by Denvercoder9 on Thursday August 12, 2021 @08:51AM (#28155599)
> They only used single letters:

> * https://www.openssl.org/news/changelog.html

From that link:

> When a release is created, that branch is forked off, and its changelog is also forked. For example, none of the changes after 0.9.8n appear in the other logs, because 1.0.0 was created after that release and before 0.9.8o.

If you look at the changelog in the v0.9.8 branch, you'll see they got up to 0.9.8zh:

https://github.com/openssl/openssl/blob/OpenSSL_0_9_8-stable...

Re:ZeroVer: 0-Based Versioning by xd1936 on Thursday August 12, 2021 @10:54AM (#28157093)
Who were you, Denvercoder9? What did you see?
Re:ZeroVer: 0-Based Versioning by Threeve303 on Thursday August 12, 2021 @11:05AM (#28157230)
The legend of Denvercoder9 continues to this day
Re:ZeroVer: 0-Based Versioning by capableweb on Thursday August 12, 2021 @08:50AM (#28155584)
ReactOS existed for 25.5 years, now on version 0.4.13.

Tor has been around for 17.3 years, now on version 0.4.7.0

Seems getting rock-solid software to >1.0 takes a rock-solid effort.

Re:ZeroVer: 0-Based Versioning by ziml77 on Thursday August 12, 2021 @09:38AM (#28156169)
ReactOS makes sense to still be at version 0. Even with all the work put into it, it's still not usable as a daily driver.
Re:ZeroVer: 0-Based Versioning by vjeux on Thursday August 12, 2021 @07:39AM (#28154980)
For React Native we do ~monthly releases and just increase by 1 each time. It’s a train model this way people know when their changes will get released. I guess we should consider bumping to 1.x at some point and keep going :)
Re:ZeroVer: 0-Based Versioning by nicoburns on Thursday August 12, 2021 @07:46AM (#28155031)
Monthly? There were 3 releases in 2019, 2 in 2020, 2 so far in 2021 if you count the imminent 0.65 release.

I guess maybe it's monthly if you count the patch releases? But you can't really claim to "just increase the number by 1 each time" when you have two separate numbers which get incremented for different reasons.

Re:ZeroVer: 0-Based Versioning by vjeux on Thursday August 12, 2021 @09:12AM (#28155854)
I haven’t worked on React Native for many years now… looks like it has slowed down! It was monthly in the first few years.
Re:ZeroVer: 0-Based Versioning by dathinab on Thursday August 12, 2021 @10:02AM (#28156486)
Skip 1.0 and 2.0 to brake people's expecting.

Like at some point just e.g. move from 0.69.0 to some arbitrary number like 7.0.0 or even 70.0.0.

Re:ZeroVer: 0-Based Versioning by simiones on Thursday August 12, 2021 @10:26AM (#28156761)
Java did that, right? From Java 1.4 to Java 5.

Also, at $WORK we have three separate but related products, each with separate version numbers that we jumped at some point to reach the same value across all 3. One of the products jumped from 3.x to 9.0 I believe.

Re:ZeroVer: 0-Based Versioning by _tom_ on Thursday August 12, 2021 @11:20AM (#28157440)
Java 5 was still v1.5, except for marketing, iirc. The 1.x versions persisted internally for a few releases.
Re:ZeroVer: 0-Based Versioning by dathinab on Thursday August 12, 2021 @12:57PM (#28158709)
Java moved from 1.4 to 1.5 and just stopped displaying the 1.

The reason was that they committed to never to any "major braking change" i.e. that there would never be a version 2.

At the same time the backwards compatibility guarantees didn't work always as good as some people liked so they decided to move from semver to something which is like "only do minor releases, but sometimes imperfect making them somewhat major releases but also somewhat not".

What I advocated for differs in that I want to keep semver. So when you move from e.g. 0.32.0 to 32.0.0 you still would only inc minor version for non braking changes and the patch version for patches.

Through this means that you now can denote path updates, as in 0.32 the minor updates are like major updates and the patch updates are like minor updates.

This can be especially useful when development release speed slows down and you want to make a new release with e.g. just fixing some API docs or just non API exposed bug fixes.

Re:ZeroVer: 0-Based Versioning by magic_quotes on Thursday August 12, 2021 @02:22PM (#28159665)
Java / OpenJDK never used semver in the first place. Also, large projects like Java have entire layers of different APIs, whose compatibility guaranties can't really be described with a single number, no matter what versioning scheme they use.
Re:ZeroVer: 0-Based Versioning by Heliosmaster on Thursday August 12, 2021 @07:43AM (#28155012)
why not switch to a year-month then, if the release process is already time-based?
Re:ZeroVer: 0-Based Versioning by emteycz on Thursday August 12, 2021 @08:52AM (#28155608)
1. cost (and risks) of switching - not just for the project itself, but across the ecosystem and all the millions of users

2. what if you need multiple releases in a month, in a day?

3. if it works, don't touch it

Re:ZeroVer: 0-Based Versioning by nick__m on Thursday August 12, 2021 @10:31AM (#28156810)
i dont have awnsers for 1 and 3 but reagarding 2 the format YYYYMMDD.NN allow you to have 100 releases a day...
Re:ZeroVer: 0-Based Versioning by jrochkind1 on Thursday August 12, 2021 @09:09AM (#28155818)
Do you have any policies around backwards compatibility? Is there any way to know if a given release has intended backwards-breaking changes or not?
Re:ZeroVer: 0-Based Versioning by joshxyz on Thursday August 12, 2021 @07:14AM (#28154803)
yup sounded like a joke until the table LOL
Re:ZeroVer: 0-Based Versioning by uncomputation on Thursday August 12, 2021 @08:00AM (#28155127)
(Just wanna make it clear that this is a joke. The footer says published April 1 and the about page states it is satire just for anyone confused.)
Re:ZeroVer: 0-Based Versioning by nightcracker on Thursday August 12, 2021 @08:06AM (#28155174)
I don't think calling it a joke is correct. It correctly self-describes as satire, which is quite different. Both use humor but one is not meant seriously whereas the other has a serious critique behind it.
Re:ZeroVer: 0-Based Versioning by tialaramex on Thursday August 12, 2021 @10:04AM (#28156508)
A good satire should have a serious point it dismisses as part of the joke. For example Swift's "A Modest Proposal" is famous for its recommendation that Ireland's problems will be solved if the Irish eat their children, but it explicitly dismisses the possibility of taxing "absentee landowners" and other wealthy people and that is what Swift thinks you should actually do.

The closest ZeroVer comes is to quote Tom Preston-Werner, "If your software is being used in production, it should probably already be 1.0.0." which is something, but could perhaps be dismissed more thoroughly as undesirable or mistaken in this document.

Re:ZeroVer: 0-Based Versioning by wott on Thursday August 12, 2021 @10:47AM (#28156988)
> For example Swift's "A Modest Proposal" is famous

Given the context, I thought for a minute that you were talking about Apple's presentation of the rationale for a successor to Objective-C.

Re:ZeroVer: 0-Based Versioning by k__ on Thursday August 12, 2021 @07:09AM (#28154775)
Many OSS projects were and still are pre 1.0 for years.

I think, it's a sign of hybris if a project owner goes 1.0 too soon.

Re:ZeroVer: 0-Based Versioning by julianlam on Thursday August 12, 2021 @07:30AM (#28154920)
... hubris? I think that's a bit much.

We went v1 once we decided our software was ready for other people to use. It meant we'd ensure compatibility via upgrade scripts, and it meant we wouldn't do irresponsible things like tell users "this release requires you to drop your database and start over"

Re:ZeroVer: 0-Based Versioning by k__ on Thursday August 12, 2021 @08:33AM (#28155412)
I think, that's the main problem with SemVer. Everyone tries to merge the major version with some kind of nebulous "readiness". While it should just be a number related to technical aspects of the software.
Re:ZeroVer: 0-Based Versioning by superjan on Thursday August 12, 2021 @09:25AM (#28155984)
And I think that is the right way to think about it. I think people stay on 0 because they think they have to implement all ideas and edgecases before it you can call it 1.0. You can also get stuck on 1.x releases in the same way (notably Java).
Re:ZeroVer: 0-Based Versioning by mytailorisrich on Thursday August 12, 2021 @07:48AM (#28155046)
If you have a set of working, useful features, however small as long as they part of your core product, and you release to the public then you have your v1.0.

IMHO, if you stay pre 1.0 for years across many releases it means you have too wide a scope for what v1.0 should be.

Essentially, your MVP is v1.0 since that the first viable product you release.

But what sometimes happens is that people imagine v1.0 as being the full vision with everything and so they never really reach it. And of course sometimes it seems that there is no sensible explanation at all for why a product is still pre 1.0 to the point of being ripe for satire, indeed (and ZeroVer is really on point the way it satirises this!).