[PATCH] upgradepath doesn't support -testing repos yet, disable scheduling

James Laska jlaska at redhat.com
Thu Sep 23 13:16:51 UTC 2010


On Thu, 2010-09-23 at 13:04 +0200, Kamil Páral wrote:
> This patch kind of reverts fbe9ee91b. We don't want upgradepath to be run
> for -testing repos, because that would effectively prevent maintainers
> from pushing into -testing. They would need to wait until that package
> gets into stable updates in more recent Fedora releases, and we don't
> want that.


> So the solution is not to schedule upgradepath for these update requests
> at all (at least until we have more complex upgradepath). That will fix
> the assertion error we had received.

Sorry Kamil, I'm in need of clarification.  Isn't 'upgradepath' listed
as a mandatory test [1] for any updates entering 'updates-testing'?  I
feel like we're missing out if we don't run the test when a package is
proposed for updates-testing.  

Re-reading the criteria [2], do I understand correctly that upgradepath
must PASS in order to be pushed into 'stable'?  If that's true, I think
I better understand the open question now.  If the result of upgradepath
would only prevent a package from being pushed to stable, why bother
running it for 'updates-testing'?  Is that correct?

Thanks,
James

[1]
https://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan#Mandatory_tests
[2] https://fedoraproject.org/wiki/Package_update_acceptance_criteria
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : https://fedorahosted.org/pipermail/autoqa-devel/attachments/20100923/1a99fb08/attachment.bin 


More information about the autoqa-devel mailing list