On Tue, Jun 9, 2009 at 9:25 AM, Jickae Davis <jick...@gmail.com> wrote:
> After carefully check, I think I am confused about continuous and snapshot,
> :(.
>
> Amanda said:
> continuous: ever time anyone checks in a change, we have a continuous build
> system that checks out the change and tries to build Chromium.
> snapshot: a snapshot build is simply a copy of chromium that was
> successfully built by the continuous build system (that is, each snapshot is
> the most recent build that did not fail for some reason).
>
> Mohomed said:
> continuous is the most recent revision that passed both unit tests and
> layout tests.
> snapshots is exactly what that word defines. Chromium keeps snapshots of
> specific revisions in history, so you can go back in time.
>
> dhhwai said:
> Continuous builds are those snapshot builds that have passed all the
> automated tests.
> Snapshot builds are current, on the fly, development builds whenever a
> developer has checked in changes for recompiling. You get a snapshot
> build whenever there is a successful compile.
>
> Let me make the question clear :
>
> Continuous : builded successfully, tested successfully
> Snapshot: only builded successfully
> tarball: the latest version that is builded and tested
> successfully while a day ends
>
> right?
>
>
Yes, the one addition is the tarball is raw source, the other two are built
binaries.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
