Chromium Version History Information.

[Stephen Cheng]

I am seeing a huge number of releases at this page: http://src.chromium.org/viewvc/chrome/releases/ . How do I know which version is stable and which is not? How can I tell if it's a stable build, beta build or dev build?

And with each release, do we have a web page which lists all the major changes made in each release? I am expecting to see a brief list of new features and fix of very important bugs, instead of the very detailed committing comments from the version control system.

It is always hard for me to understand why the official chrome download page (https://www.google.com/intl/en/chrome/browser/) doesn't show any version number, neither does it show any new features with each release.

[Shezan Baig]

I use this page to get stable/beta/dev version info:
http://omahaproxy.appspot.com/viewer

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Rachel Blum]

I am seeing a huge number of releases at this page: http://src.chromium.org/viewvc/chrome/releases/ . How do I know which version is stable and which is not? How can I tell if it's a stable build, beta build or dev build?

http://omahaproxy.appspot.com shows the recent ones. I don't know if we track it on a web site for older builds - why would you need that?

And with each release, do we have a web page which lists all the major changes made in each release?

http://googlechromereleases.blogspot.com/

 

- rachel

--

[Shanfeng Cheng]

I guess I can find all the stable releases from the blogspot site you mentioned by searching for all posts with the title "Chrome Releases: Stable Channel Update".

 

---

Shanfeng Cheng

[Stuart Morgan]

On Mon, Nov 18, 2013 at 11:41 AM, Stephen Cheng <sfc...@gmail.com> wrote:

It is always hard for me to understand why the official chrome download page (https://www.google.com/intl/en/chrome/browser/) doesn't show any version number

Because Chrome users shouldn't have to care about versions; Chrome simply continues to get better as it auto-updates. Chrome is explicitly not version-number-driven the way a lot of other software is.

 

neither does it show any new features with each release.

Existing users should almost never have any reason to go to that page, given the autoupdate system, and "what's new since last version" isn't meaningful to new users.

-Stuart

[Shanfeng Cheng]

Well, I don't agree with that as a user. I have no problem with auto-updates. But I do want to know what interesting new features are being rolled out so that I can check them out.

There are two kinds of people in the world. One kind just enjoys taking whatever is being served. The other kind likes to examine what is being served in the plate before eating it. Probably I have to admit that the first kind is the majority. But the second kind of people is clearly not an ignorable portion.

 

 

 

---

Shanfeng Cheng

 

From: Stuart Morgan

Date: 2013-11-18 18:57

To: sfcheng

CC: chromium-dev

Subject: Re: [chromium-dev] Chromium Version History Information.

[sam]

How about link to "Stable updates": (http://googlechromereleases.blogspot.tw/search/label/Stable%20updates)?

Sam Tsai

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Shanfeng Cheng]

Thanks for the link. That's more convenient than doing the search. I will bookmark it.

 

I wonder if there is any naming convention on the version numbers so that we can easily tell if it's a beta or stable release? I remember seeing something about it somewhere but can't find it now.

 

---

Shanfeng Cheng

[PhistucK]

Usually -

x.x.x.(0 - 2) would be non branch canary or dev builds.

x.x.x.(2 - 10) could be canary builds of a stabilizing branch (to be released to dev).

x.x.x.(10 - 15) could be dev builds of a stabilizing branch (to be released to beta).

x.x.x.(15 - 40) could be beta builds.

x.x.x.(41+) could be stable builds.

☆PhistucK

[Victor Khimenko]

On Tue, Nov 19, 2013 at 9:14 AM, Shanfeng Cheng <sfc...@gmail.com> wrote:

Thanks for the link. That's more convenient than doing the search. I will bookmark it.

 

I wonder if there is any naming convention on the version numbers so that we can easily tell if it's a beta or stable release? I remember seeing something about it somewhere but can't find it now.

Such conventions could not actually exist because this decision is done post-factum: when time comes build is promoted to dev channel but promotion to beta and finally to stable happens when it's declared "stable enough". There are rought estimates for how long each step takes thus you can guess from the version number what is what, but this is not 1-to-1 mapping.

[Shanfeng Cheng]

This is very helpful. Thanks a lot for the tips.

 

---

Shanfeng Cheng

[Eric Roman]

http://omahaproxy.appspot.com/history

[Shanfeng Cheng]

Great link! Thanks for sharing.

 

---

Shanfeng Cheng

[Eric Roman]

You may also enjoy these sites for tracking new features:

http://peter.sh/

https://plus.sandbox.google.com/+FrancoisBeaufort/posts