Yes, many people do download the latest builds by hand; it's not really that hard after all.
In another post ( http://groups.google.com/group/chromium-discuss/browse_thread/thread/8e75e068e77f54f4/79b0f68ac88972fa?#79b0f68ac88972fa ), [email protected] mentioned he uses a batch file with curl and 7z to automate the process, and that script does basically what the third party updater programs do. You can easily modify that batch file to accept a parameter of which build number to retrieve instead of automatically retrieving the latest build. You can see all the Continuous builds from http://build.chromium.org/buildbot/continuous/win/?C=N;O=D (There are similar directories for "mac" and "linux".) Managing different builds is fairly straightforward: each build has its own build number. It is probably best to also rename each downloaded ZIP file to include the build number and also to extract into a directory with the build number. Then it is really easy to manage all the different builds. All the builds only directly influence the Dev channel releases. The Continuous builds have passed all the automated unit and layout tests. These builds become candidates for the Dev channel releases. Technically, I believe none of the ongoing builds ever corresponds directly with any Dev, Beta, nor Stable release. As far as I know, any build that is branched for a release version may or may not have specific individual patches applied to it to create the final release version. So none of the Stable nor Continuous builds will ever correspond exactly to a release version. On Jun 18, 11:43 am, loomy <[email protected]> wrote: > There are a number of chromium updater programs online, but they don't > know how to do anything but download the very latest chromium build. > So how do people who test chromium for release and such download > particular builds automatically and manage different builds? Is > everyone just downloading or building by hand? > > Google should provide information about which build corresponds with > which channel version and which release candidate for each channel, > etc. Then these updater programs can be improved. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
