Are you going to handle it in a manner similar to a security release and give the maintainer a few days to commit a patch before the post goes live?
No, I don't personally intend that, quite simply because they're not security reviews and there is nothing to be lost by having the post appear before things are "fixed". Save for this very first review, for Printer-Friendly Pages, our queue is filled with people who /want/ these reviews, and have knowingly agreed to have the results made /public/. There's no clock to beat, nor embarrassment you didn't bring upon yourself ;) The intent of the reviews is to increase code /quality/, which /only occasionally directly/ equates to an end-user benefit. Sure, you can fix bugs and speed up a function, and perhaps make this work a little more closely to core but, to the end-user, it's not going to make a huge amount of difference - they may notice some of the more UI-related things, or that something is a little faster, but they're not going to know if you committed faster good code or faster crappy code. -- Morbus Iff ( they should rename controlled chaos to morbus droppings ) Technical: http://www.oreillynet.com/pub/au/779 Enjoy: http://www.disobey.com/ and http://www.videounderbelly.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus