It's a good point that more people testing is probably better. On the other hand, there's probably some annoying overhead in pushing a release to the auto updater. Given that there's been at least 30 updates to trunk since the build 8857 that Mohamed mentioned, it makes sense for them to make them available to dev channel at a specific interval.
For those don't know the public has access to the latest builds here: http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/ It's not as convenient as the auto updating when a new build is released on dev channel but it allows you faster access at least. On Feb 1, 5:57 am, PJC <[email protected]> wrote: > 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 --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
