Arguably, CI is a must to have for any commit model. If there's no CI then reviewer has to apply the patch and do build-n-test dance to make sure that modifications aren't breaking the build. Thus, CTR isn't really hanging on a need for a robust CI; but CI would be a great help for sure.
Cos On Sat, Dec 27, 2014 at 11:37PM, Mark Grover wrote: > I completely agree with Roman and Peter. Right now, we don't have good > altering/monitoring that enable us to have a quick turnaround time to fix > things when they break. I'd think that'd be a pre-requisite for making the > project CTR. I am glad and excited to see it being very close to done. > > On Sat, Dec 27, 2014 at 11:21 PM, Peter Linnell <[email protected]> wrote: > > > On Sat, 27 Dec 2014 18:28:31 -0800 > > Roman Shaposhnik <[email protected]> wrote: > > > > > On Sat, Dec 27, 2014 at 7:26 AM, Jay Vyas > > > <[email protected]> wrote: > > > > If we wanna do CTR ... > > > > Can we just do it into master? > > > > I realize it will break but that what CI is for. > > > > > > On that note, I'd be a strong +1 on CTR once we get > > > our CI fully functional again. Without it, I guess I'm -0. > > > > > > The good news is, I think I'm pretty close to getting > > > it done by the end of the year ;-) > > > > > > Thanks, > > > Roman. > > > > I had been pondering this and read all the threads. My instinctive > > reaction was no, but as Roman pointed out, we need a reliable CI setup > > we can all monitor easily. With that fixed I'm a +1. > > > > @Roman, what can we do to help getting the CI system right side? > > > > Thanks, > > > > Peter > >
signature.asc
Description: Digital signature
