Re: QA Improvements on 4.2.0

Hi - I agree and wrote the same on a different thread the other day. Regards, Dave > On Oct 24, 2017, at 3:28 AM, Pedro Lino wrote: > > Hi Raphael, all > >> I believe the 4.1.4 shows us, that we have to do a better job in QA. A >> minor release should never go to a

Re: QA Improvements on 4.2.0

Hi Raphael, all > I believe the 4.1.4 shows us, that we have to do a better job in QA. A > minor release should never go to a rc5. I believe we all (and I pointing > my finger to myself) underestimated the regression risk at the 4.1.4. +1 > So, to do a better job in the 4.2.0 I propose the

Re: QA Improvements on 4.2.0

I like all this. In addition, I would like to get set up to do code review. I don't like the idea of changes going out to millions of users having only been seriously examined by one programmer - even if I'm that programmer. For both code review and testing, we need more active developers in

QA Improvements on 4.2.0

Hi all, I believe the 4.1.4 shows us, that we have to do a better job in QA. A minor release should never go to a rc5. I believe we all (and I pointing my finger to myself) underestimated the regression risk at the 4.1.4. So, to do a better job in the 4.2.0 I propose the following changes.