Mailing list convention proposal

Mo Morsi mmorsi at redhat.com
Tue Feb 28 14:41:42 UTC 2012


On 02/28/2012 07:04 AM, Petr Blaho wrote:
> Hi,
>
> yesterday I spent a huge amount of time to find out why there are some failing rspec tests for conductor - spec/controllers/api/images_controller_spec.rb
>
> I found that there is a bug https://bugzilla.redhat.com/show_bug.cgi?id=796783 with multipatch as a solution - part for conductor and part for aeolus-image-rubygem
>
> And these tests were failing with aeolus-image-rubygem installed by yum.
>
> To make them work I had to build rubygem-aeolus-image rpm from source and install it.
>
>
> So I think it would be good if developers working on this type of patches should send an email with message that rubygem from source is needed after they pushed their patches to repo.
>
> These type of emails should have something like [ANNOUNCEMENT conductor] or [ANN conductor] so development community can filter these emails and notice them.
>
> What do you think?
>

Hrm, when working / running tests of the latest HEAD, I will often just 
assume that I need to be working against the latest revision of all 
components / dependencies (at least the ones we control).

Running the tests from any given release obviously should work against 
the dependencies in the repo at the time of that release, but the 
development HEAD is generally assumed to be a little more unstable, 
requiring more care to keep dependencies in sync when running code 
and/or tests.

That being said, I agree that we need to be better at representing the 
exact dependencies any give patch will require. All in all for tests, 
new code, etc, a patch should detail exactly what it needs to run 
successfully including specific versions / commits of Aeolus components 
and other dependencies if possible. I believe this should address the 
issue at hand w/out adding the extra overhead of additional emails 
(unless you feel strongly about the benefit of those?)

Additionally, the rule has always been that if anyone is adding an 
additional external dependency. It is up to them to package it up and 
make sure it gets into Fedora, fedorapeople.org/repos/aeolus, and 
anywhere else it needs to be. The patch adding the dependency to Aeolus 
should not be pushed until that is the case.

   -Mo



More information about the aeolus-devel mailing list