----- "James Laska" jlaska@redhat.com wrote:
On Fri, 2010-01-15 at 08:40 -0500, Kamil Paral wrote:
----- "Kamil Paral" kparal@redhat.com wrote: There is also one question that is directly connected to this
topic.
Which tags do we want to search through when looking for previous builds? a) Currently we search through stable, -updates and
-updates-testing.
b) Would it make sense to search also through -updates-candidate? The differences would always show to the very latest build, doesn't have to be released. c) Or the other way round, would it be better to search through only
stable and -updates (skip -updates-testing)? When more builds are in testing repo, the differences would be displayed always against the latest build in stable repos (stable
or
-updates).
re: solution#2 - Will probably has good historical perspective here, but this seems sensible to me.
/me walks through a mental exercise ...
A package-0.0 exists in dist-f12 (or dist-f12-updates). An updated version package-0.1 lands in updates-testing and turns out to be bad. Then, a new package-0.2 is built and tagged for updates-testing. I don't think we'd want to compare package-0.2 with package-0.1.
That is exactly what I considered. So this is a bonus point for c).
I believe we want to compare against the previous generally available package (and allow for an optional over-ride if desired?). I don't consider updates-testing to mean generally available. True, it might mean that some of the same issues identified from the previous comparison, will be displayed again for review. When we need to review test results for a package that was released with a problem, I'd prefer looking at one test summary, instead of potentially piecing together the results from multiple comparisons against interim test versions of the package.
Thoughts/concerns?
Thanks, James
autoqa-devel mailing list autoqa-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/autoqa-devel