Why fixes of broken dependencies are not automatically tagged into F17

[Vít Ondruch]

Dne 10.4.2012 08:23, Bruno Wolff III napsal(a):
> On Tue, Apr 10, 2012 at 08:15:14 +0200,
>   Vít Ondruch <vondruch at redhat.com> wrote:
>>
>> Actually the reason why I am asking is that there is a lot of broken 
>> dependencies, because of Ruby update. Some of them are already fixed, 
>> but not accepted due to freeze. Proposing all this fixes as NTH would 
>> be nightmare for me as well as for the blocker review meeting. I'd 
>> love to see this process simplified/automated.
>
> If they aren't breaking things in the default install or the 4 desktop
> live images they aren't going to be accepted as NTH since they don't
> affect the compose and they can easily be fixed with updates.

Not sure if this is in support of my case or against :)

But as you says "If they aren't breaking things in the default install 
or the 4 desktop
live images", then they should go into updates immediately after 
spending some testing period in Bodhi and they should not wait for unfreeze.

Vit