Re: Updates: karma and timeouts
On Thu, 12 Jul 2012 15:09:05 +0200, Darryl L. Pierce wrote: I think if those packages are languishing, it's like the packager was already notified and chose not to push. Package goes into testing with the goal to get into stable. Therefore by default it should go into stable when it gets approved for it. There must be a specific reason one puts package into testing and later not wanting to push it to stable. If such reason appears one revokes the package anyway. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Updates: karma and timeouts
On Fri, Jul 13, 2012 at 08:37:19AM +0200, Jan Kratochvil wrote: On Thu, 12 Jul 2012 15:09:05 +0200, Darryl L. Pierce wrote: I think if those packages are languishing, it's like the packager was already notified and chose not to push. Package goes into testing with the goal to get into stable. Therefore by default it should go into stable when it gets approved for it. But tacit approval is not the same as having been tested by third parties and verified as working. There must be a specific reason one puts package into testing and later not wanting to push it to stable. If such reason appears one revokes the package anyway. And that reason mam be I want three people to test it and give it karma and it's not happened yet. No reason to revoke the package, it just has been tested by enough people in the packager's opinion. -- Darryl L. Pierce mcpie...@gmail.com http://mcpierce.multiply.com/ What do you care what people think, Mr. Feynman? pgpQ2Oye7TM8P.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Updates: karma and timeouts
On Wed, Jul 11, 2012 at 04:38:19PM -0700, Adam Williamson wrote: Hey, folks. So I've had a feeling lately that the amount of karma being filed on updates has dropped - especially since proventesters was axed - but I don't have hard numbers. I've put it on my todo list to check into this and do what I can to fix it, though. Testers, as I always nag, please keep up karma efforts - even though proventesters is inactive at present, updates still need karma! Whether you're a proventester or not, please keep up filing karma, for F16 as well as F17. Thanks. Secondly - something developers can do: remember that there's a 7-day / 14-day timeout rule for your updates! You can push non-critpath updates 7 days after they go to updates-testing even if they have zero karma, and critpath updates after 14 days. 14 days is kind of a long time and it's easy to forget, so it's probably a good idea to sign into Bodhi every so often and check if you have any updates sitting in updates-testing where the timeout has expired and you can now push them stable if you so choose. I have noticed a few updates where the deadline expired some time ago that haven't been pushed yet. Obviously in some cases the devs may be choosing not to push the updates until they get some karma, but I thought I'd just put out a general reminder just in case. Thanks folks! An email goes out letting the packager know their package has reached the 7 day minimum. I think if those packages are languishing, it's like the packager was already notified and chose not to push. -- Darryl L. Pierce mcpie...@gmail.com http://mcpierce.multiply.com/ What do you care what people think, Mr. Feynman? pgpHE0IpC5rWF.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Updates: karma and timeouts
Hey, folks. So I've had a feeling lately that the amount of karma being filed on updates has dropped - especially since proventesters was axed - but I don't have hard numbers. I've put it on my todo list to check into this and do what I can to fix it, though. Testers, as I always nag, please keep up karma efforts - even though proventesters is inactive at present, updates still need karma! Whether you're a proventester or not, please keep up filing karma, for F16 as well as F17. Thanks. Secondly - something developers can do: remember that there's a 7-day / 14-day timeout rule for your updates! You can push non-critpath updates 7 days after they go to updates-testing even if they have zero karma, and critpath updates after 14 days. 14 days is kind of a long time and it's easy to forget, so it's probably a good idea to sign into Bodhi every so often and check if you have any updates sitting in updates-testing where the timeout has expired and you can now push them stable if you so choose. I have noticed a few updates where the deadline expired some time ago that haven't been pushed yet. Obviously in some cases the devs may be choosing not to push the updates until they get some karma, but I thought I'd just put out a general reminder just in case. Thanks folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Updates: karma and timeouts
On Wed, Jul 11, 2012 at 16:38:19 -0700, Adam Williamson awill...@redhat.com wrote: 14 days is kind of a long time and it's easy to forget, so it's probably a good idea to sign into Bodhi every so often and check if you have any updates sitting in updates-testing where the timeout has expired and you can now push them stable if you so choose. I have noticed a few updates where the deadline expired some time ago that haven't been pushed yet. Obviously in some cases the devs may be choosing not to push the updates until they get some karma, but I thought I'd just put out a general reminder just in case. Thanks folks! Bohdi will send a notification email when the updates can first be pushed and you get occassional reminders after that. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Updates: karma and timeouts
On Wed, 2012-07-11 at 20:57 -0500, Bruno Wolff III wrote: On Wed, Jul 11, 2012 at 16:38:19 -0700, Adam Williamson awill...@redhat.com wrote: 14 days is kind of a long time and it's easy to forget, so it's probably a good idea to sign into Bodhi every so often and check if you have any updates sitting in updates-testing where the timeout has expired and you can now push them stable if you so choose. I have noticed a few updates where the deadline expired some time ago that haven't been pushed yet. Obviously in some cases the devs may be choosing not to push the updates until they get some karma, but I thought I'd just put out a general reminder just in case. Thanks folks! Bohdi will send a notification email when the updates can first be pushed and you get occassional reminders after that. I know, but I suspect a lot of people (like me) filter Bodhi mail into its own folder, which (also like me) they don't check often enough... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
