Linked by Thom Holwerda on Fri 9th Jan 2009 08:43 UTC, submitted by amjith
Thread beginning with comment 342822
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Not a major update (so far)
by Moredhas on Fri 9th Jan 2009 20:57
in reply to "RE[2]: Not a major update (so far)"
I know there's an etiquette to observe when assigning version numbers to your software. Major internal updates get a number before the point, while minor internal or interface changes get one after it, but really, it's their software. If they want to call it 2.0, I won't begrudge them that. It seems like a pretty big internal change to enhance existing CSS support and switch to completely different HTTP code. This is pre-beta, maybe the final release of 2.0 will have enough visible feature changes to justify that number.






Member since:
2005-07-06
I'd agree with that. As I said, I like Chrome, and yes, it's great that they update often. In some ways, having small updates is easier for users to deal with versus a large scale change where so many things have changed it's difficult to get your bearings.
My point is though, compare version 1 (which itself was hardly feature complete) to the forthcoming version 2. Does it warrant a whole version number? Not from what I've seen so far. v1.5 at the very least.