On Wed, 2008-11-26 at 19:12 +0100, Patrice Dumas wrote: > > Ok. You still haven't explained what checks were done, especially > between pending and stable or testing. > > > The main reason we haven't inserted any automated QA is that to get a > > correct picture of what the distro would look like with that update > > added takes a full compose, to ensure we get the right view of multilib, > > and that we don't have an older copy of the package update floating in > > repos resolving deps it shouldn't, etc... The compose process itself is > > extremely time and resource consuming and it unfortunately hasn't been > > as high of a priority to tackle as it should have been. > > Right. This is a good reason, especially if compose takes one day. Still > it doesn't explain the other delays. I still can't see what takes time > besides composing, nor why there is a pending state. I guess I'm not fully understanding your question. A user submits an update to bodhi, and when they are satisfied that they have all the builds added correctly and that the text is right, they request it be pushed either to testing, or to stable. After that the only delay is the time it takes for me, the pusher, to handle the pending requests. The checks are quite simple in bodhi I do believe, I think it just checks to make sure what you requested is tagged appropriately at the time of request. The rest of it is left up to users of updates-testing to report any problems to the maintainer, either through bugzilla or bodhi karma, or both. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
