Re: Minor change in the per patch process.

On Thu, Aug 16, 2012 at 09:32:20PM -0400, Robert Middleswarth wrote:

Part of the process now include creating rpm packages. http://jenkins.ovirt.info/view/patches/job/patch_engine_create_rpms/ This allows people to download and test packages based on the change if they want to.

I wonder if this is needed by people. For me it duplicates the number of emails per change... BTW, I see that a failed job http://jenkins.ovirt.info/job/patch_vdsm_unit_tests/486/console does not set V-1 on the change. Could this be fixed? I'd like the poster and human reviewer to be perfectly aware that a change breaks unit tests. Regrads, Dan.