On the 0x3B0 day of Apache Harmony Mikhail Loenko wrote: > We have suites which most of the time are green and suites that most > of the time are red. We should think of including "mostly red" suites > to precommit testing so that we have all green when we decide to make > a real release
if mostly red aren't too slow.. > Thanks, > Mikhail > > 2007/12/18, Tim Ellison <[EMAIL PROTECTED]>: > > Stepan Mishura wrote: > > > On 12/17/07, Tim Ellison <[EMAIL PROTECTED]> wrote: > > >> Stepan Mishura wrote: > > >>> What criteria do you use to define if the build is stable enough? > > >> The opinion of people who work in each area saying it is stable. > > >> > > > > > > Sure, the final decision is made by people. > > > > > >> The tests and scenarios are there to give us good information to work > > >> with, but in the end it is 'people over process' that decide. > > >> > > > > > > But if regressions have tendency to get accumulated then the next > > > questions start to disturb me: what is wrong with the process? when we > > > should try to make everything 'green' on the snapshot status page? > > > > Absolutely! Don't get me wrong. Having a full set of test suites and > > keeping them 'green' is very important. There's too much information to > > understand without the reassurance of constantly passing tests. > > Regressions and failures need to be understood and addressed. > > > > Today's question is: is this revision a stable point in the code that we > > can publish as a basis for ongoing development? I think it looks good > > enough to declare a milestone. I'm looking for others' opinion in areas > > of code I'm less familiar with. > > > > Regards, > > Tim > > > -- Egor Pasko
