Are you talking about waiting for a Chromium developer to confirm the automatic Chromium Build Finder posted by timeshift? I'm pretty sure that will never happen because the Build Finder was built by some third party outside of Google, and it's certainly not endorsed by Google/the Chromium developers.
No matter if you are talking about the Chromium "snapshot" builds ( http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/?C=M;O=D ) or the Chromium "continuous" builds ( http://build.chromium.org/buildbot/continuous/?C=M;O=D ), neither is meant for automatic nor regular installs nor normal use by users. (Also, I believe the difference between snapshot and continuous versions is that the Continuous versions have passed all the layout tests, but a Snapshot version just has a successful compile.) These builds (including the Dev channel builds) are all latest development testing versions, exactly for that purpose: testing. You can expect to find plenty of problems, annoyances, incompatibilities and regression errors in such builds. Such builds should only be installed by users who are willing to accept such problems, and wish to try out the status of the latest development versions. On Feb 4, 7:58 am, Nat <[email protected]> wrote: > Even the latest version (build 9136) still has a problem > withhttp://blogs.msdn.comwhere the content is blank... > > On Feb 4, 10:16 pm, PJC <[email protected]> wrote: > > > > > Thanks Erek, > > > I think it'd be good if that URL was publicised better - I wasn't > > aware of it at all. > > > I'm now running build 9029, which not only resolves the 2.0.159 > > problems, it also seems to work correctly with Live Mail (!) > > > -PJC > > > On Feb 1, 6:13 pm, Erek Speed <[email protected]> wrote: > > > > 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 -~----------~----~----~----~------~----~------~--~---
