FCP 20190401-ci_policy: CI policy

[Hans Petter Selasky]

Hi,

If the fallouts could be better organized through some simple 
guidelines, that would be more accepted I think:

1) Don't commit stuff before going off work. Even though a change looks 
innocent, it might break something and you'll need to fix it.

2) Organize big changes going into the kernel, to ease debugging and 
getting things back on track again.

3) If your patch is risky, commit it on a Monday. Don't wait until Friday.

Failure to follow the rules may have consequences like other senior 
developers kicking in and doing temporary reverts until issues are resolved.

--HPS