Re: Is AutoQA Ready for a Release

[Tim Flink]

On 05/19/2011 02:26 AM, Kamil Paral wrote:
> > During the phone conference two weeks ago, we talked about
> trying
> > to release more frequently. The goal that I remember setting is 
> > evaluating release readyness every 2 weeks.
> > 
> > It has been 2 weeks since then and it's time to evaluate release 
> > ready-ness!
> > 
> > Unless there is something that I'm not understanding, my vote
> > would currently be "no". I'd like to see the spam-reduction code in
> > place before we make the first release - I should have something
> > pushed up to a git branch for initial review in the next day or
> > so.
> > 
> > Any other thoughts?
> > 
> > Tim
>  
>  No, it's not. We don't have any of the important changes done yet. I
>  have worked on improved result reporting methods inside test.py,
>  vhumpa on plaintext template and jskladan on depcheck filtering. All
>  those jobs seem to be almost finished, now we need to merge it
>  together (it's very related) in one common branch and propose as a
>  patch. I guess that will take another week. 
Cool, it sounds like we're in agreement unless someone else disagrees. I
just wanted to make sure that we didn't forget to evaluate.

>  Regarding spam-reduction, do you have some info about the necessary
>  changes in Bodhi going live in the meantime, Tim? 
I've not heard anything, no.

Tim