Linked by Thom Holwerda on Tue 15th Sep 2009 22:21 UTC
Google Only a year after Google's Chrome entered the browser market, we're already hitting version 3. While Chrome 3 had been available in the developer and beta channels for a while now, the company has now released the first stable Chrome 3 version. Technically, this means Chrome 3 has been released.
Thread beginning with comment 384329
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: evolving
by JrezIN on Wed 16th Sep 2009 12:20 UTC in reply to "RE[2]: evolving "
JrezIN
Member since:
2005-06-29

the think is, they usually are REALLY stable... I'm using them in about 4 different computers for months... hardly any problem at all. (just for the records, Windows OSes. I know mac and linux versions aren't up to these standards yet, but they're evolving fast too and they'll probably be after a stable release in each OS)

It makes all the difference when this kind of stability attracts real users (non-developers) to the development community and feedback grows a lot with this. It's a win-win situation.

Edited 2009-09-16 12:22 UTC

Reply Parent Bookmark Score: 2

RE[4]: evolving
by Adurbe on Wed 16th Sep 2009 14:40 in reply to "RE[3]: evolving "
Adurbe Member since:
2005-07-06

what I was trying to convey is that you shouldn't recommend alpha software as 'stable'

stable = stable

The word stable is often to quickly used in computing. Stability takes time and diverse testing to establise. (take Debian as an extreame example)

I know I for one would not let the dev edition be deployed within our company. Not in a million years. Stable... I'll listen

Edited 2009-09-16 14:40 UTC

Reply Parent Bookmark Score: 2

RE[5]: evolving
by werfu on Wed 16th Sep 2009 15:38 in reply to "RE[4]: evolving "
werfu Member since:
2005-09-15

I think he says that the development trunk is "stable" meaning that the functionality committed in it works and the possibility that things gets broken don't happens often. I think this is related to developpers development model. They must use fork and commit to the main tree once a feature is complete/stable. You know, commiting something that don't compile or isn't free of show stoppper bug is somewhat wrong practice and considered rude.

Edited 2009-09-16 15:39 UTC

Reply Parent Bookmark Score: 1