Erek, in the very first reply to this topic, Mohamed stated:
"Hi Evan, This has been fixed in the latest build. Chromium 2.0.160.0 (Developer Build 8857)" My comments are in light of that statement. Yes, I understand the Dev build(s) are there for bug-finding, etc, but when bugs in that build *have been found and fixed*, wouldn't it make sense to release that later build, or at least allow those of us who are running the Dev build a mechanism to easily obtain such a later build so that rather than using a different browser (my solution), we are continuing to test Chrome and therefore finding any NEW bugs that may be present. As it is, I (for one) am not finding any new issues, nor testing Chrome *at all* at the moment simply because the only released Dev build is unusable on a large number of sites. Surely, if a large number of testers is what is wanted in order to find bugs, then it makes sense to provide an accelerated build to those very testers when a major bug is discovered ***and fixed***. That's my point. -PJC On Jan 31, 2:54 pm, Erek Speed <[email protected]> wrote: > Of course, we'd all like to have bug free versions at our fingertips, > the dev version isn't supposed to be that version. Technically, its > main purpose isn't to facilitate casually surfing the web, but to > allow the testing of ideas which may or may not completely break > things. > > The solution provided by dhhwai is the correct one in that if you want > something that works, you should be using a stable release. > > I can understand where you're coming from, but it just doesn't make > sense considering the purposes of the releases. It makes less sense > considering the predicted once a week predicted release schedule for > the dev channel. > > Erek > > On Jan 31, 5:37 am, PJC <[email protected]> wrote: > > > > > I suspect shadowrun was actually hoping to get the later .160 build, > > that supposedly fixes our issue. > > > What's quite frustrating is that there seems to be such a long delay > > in getting a new build out to the dev channel, when there's an > > acknowledged major bug in the current (.159) build that has already > > been *fixed* in later builds... > > > -PJC --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
