Re: Why fixes of broken dependencies are not automatically tagged into F17
Dne 6.4.2012 18:57, Jared K. Smith napsal(a): On Fri, Apr 6, 2012 at 8:11 AM, Vít Ondruchvondr...@redhat.com wrote: I am wondering why fixes of broken dependencies are not automatically tagged into F17 (of course after staging in Bodhi), when the situation couldn't be worse by such fix. If F17 is supposed to stabilize during freeze, such fix is definitely stabilizing IMO. Am I missing something? If it's stabilizing, then propose it as a NTH fix, and the QA team will help vote it up or down in the blocker review meetings. http://fedoraproject.org/wiki/QA:SOP_nth_bug_process -- Jared Smith 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. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why fixes of broken dependencies are not automatically tagged into F17
On Tue, Apr 10, 2012 at 08:15:14 +0200, Vít Ondruch vondr...@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. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why fixes of broken dependencies are not automatically tagged into F17
Dne 10.4.2012 08:23, Bruno Wolff III napsal(a): On Tue, Apr 10, 2012 at 08:15:14 +0200, Vít Ondruch vondr...@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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why fixes of broken dependencies are not automatically tagged into F17
On Tue, Apr 10, 2012 at 08:41:16 +0200, Vít Ondruch vondr...@redhat.com wrote: Not sure if this is in support of my case or against :) 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. By they I meant bugs, not the fixes. If the fixes don't fix blockers or can be fixed in updates, then they wait until after the freeze. This is to avoid new breakage. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why fixes of broken dependencies are not automatically tagged into F17
On Fri, Apr 6, 2012 at 8:11 AM, Vít Ondruch vondr...@redhat.com wrote: I am wondering why fixes of broken dependencies are not automatically tagged into F17 (of course after staging in Bodhi), when the situation couldn't be worse by such fix. If F17 is supposed to stabilize during freeze, such fix is definitely stabilizing IMO. Am I missing something? If it's stabilizing, then propose it as a NTH fix, and the QA team will help vote it up or down in the blocker review meetings. http://fedoraproject.org/wiki/QA:SOP_nth_bug_process -- Jared Smith -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
