On 02/24/2014 12:12 AM, Reindl Harald wrote:
One potential workflow bug with this karmic automatic-push-to-stable: under the normal time-delayed path, any editing of the build reverts the package set to pending. Yet if the package set is being pushed to stable thanks to meeting the karma threshold, editing the build seems to have no effect (from the log in the link given, bodhi automatically triggers a push within 4 seconds, meaning the edited package set is basically never tested)https://admin.fedoraproject.org/updates/FEDORA-2014-2922/libreoffice-4.2.1.1-1.fc20?_csrf_token=a6a024f6e2d35ad3f3333b8666c1244e215a6aa2 how can people pretend "installation went smoothly, no issue detected during basic document manipulation" for packages which are not installable at all due dependencie problems?
What would be a good solution here -- invalidate the karma votes? (can be done either by resetting all those votes to zero, or - to better preserve the event log - by inserting a pseudo-vote with equal magnitude but opposite sign to cancel out the previous votes)
Or perhaps impose a mandatory delay similar to the delay that would have taken place anyway had no karma votes taken place?
Best regards, -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: salimma@xxxxxxxxxxxxxxxxx | GPG key ID: A36A937A Jabber: hircus@xxxxxxxxxxxxx | IRC: michel-slm@xxxxxxxxxxxxxxxx () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
