News for hackers. Stuff that matters.
Re:Chrome 60 Beta by benmarten on Tuesday June 13, 2017 @07:43PM (#14549634)
Chromes versioning does not make any sense; do they have 60 breaking changes?
Re:Chrome 60 Beta by sowbug on Wednesday June 14, 2017 @12:36AM (#14550671)
It's really simple. The first number increments when a new release branch is cut off master, about every 6 weeks. The second is always zero. The third is a build number, which is an incrementing global.

There were exceptions in the early days when the team was still figuring things out. For example, release-branches were cut more sporadically, and the middle number was used to sorta-kinda represent smaller feature changes.

You might be thinking of release dates tied to a set of completed product features. Chrome doesn't work that way. The team ships on a regular schedule, holding back features that aren't ready for the public. Frequent releases help mitigate the urge for individual teams to ship low-quality stuff just because the next release train was a long and/or unpredictable time in the future.

Re:Chrome 60 Beta by CamelCaseName on Tuesday June 13, 2017 @07:47PM (#14549666)
Re:Chrome 60 Beta by benmarten on Tuesday June 13, 2017 @07:58PM (#14549727)
Looking at the changes in 59; doesn’t seem any breaking change to me rather than features

It just seems ridiculous to me to have 4 major releases in ‘17 alone

Re:Chrome 60 Beta by charrondev on Tuesday June 13, 2017 @08:30PM (#14549894)
If understand they do it on a schedule. A new major release every 6 weeks. Dev bumps to beta, beta bumps to stable, and the old stable is retired.
Re:Chrome 60 Beta by colemickens on Tuesday June 13, 2017 @08:41PM (#14549943)
>It just seems ridiculous to me to have 4 major releases in ‘17 alone

Hm, why is that ridiculous? Do you just mean in terms of having "breaking changes" every 3 months? I guess I've never heard of someone bit by this... they'd have to be going out of their way to force a downgrade to trigger breakage from this, no?

Re:Chrome 60 Beta by DiabloD3 on Tuesday June 13, 2017 @08:09PM (#14549784)
Major number is incremented when any user facing data or setting changes (ie, ~/.chrome might not be backwards compatible anymore 100% safely).

Minor number is incremented whenever.

The number that is most important is the third number, the four digit build number, which increments monotonically and never resets. That is a more meaningful number than the first two, IMO anyways.

Re:Chrome 60 Beta by dbbk on Wednesday June 14, 2017 @06:15AM (#14551687)
No, Chrome is not semver. Also there should be no breaking changes according to web standards.