[LLVMdev] When To cvs update ?

[Chris Lattner]

On Sun, 8 Feb 2004, Reid Spencer wrote:

> I've noticed lots and lots of CVS activity on LLVM in recent weeks. I
> keep wanting to update and rebuild but I'm *scared* of it :) The LLVM
> team seems to work around the clock so I've disabled my cron job to auto
> check out and rebuild LLVM each night.

:)

> It was failing because it checked out a few times in the middle of
> logical groups of commits. What's the general policy on commits between
> releases? Are commits always supposed to at least compile? Should they
> pass all regression tests?  How should I know when to "cvs update" my
> local tree? Is there a preferred "quiet" time when its safe to update?

The general policy is that we should be strictly monotonically increasing
in quality.  While we occasionally make mistakes and have temporary
regressions, things should always be improving, and widespread breakage
_should not happen_.

Unfortunately there is a small problem with the use of CVS, and it not
having atomic commits.  Because of this, it's possible that you could get
a tree between checkins, but this should be rare in practice.  It's also
possible that someone forgot to check in part of a change, but that should
hopefully be even more rare. :)

I'm not sure what a good way to address this is.  The nightly tester runs
at 3:05AM CST, so that is currently an assumed "known good" time, when
people should have checkins half way in.  If you'd like to pull then, or
shortly after then, that might work...

-Chris

-- 
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/