On 12/10/2009 01:14 PM, David Gerard wrote: Especially on a project where previous expectations haven't been met, I'm very reluctant to give dates without reasonably good data to back them up. However, we're making good progress toward having a date. Aaron is finishing exams this week, and will be joining us in San Francisco next week. While he's here, we'll be meeting with the usability folks to come up with final-ish designs that improve FlaggedRevs usability and fit it in to the upcoming usability work. That in hand, we'll make a list of all the remaining work and put some relative estimates on it. From there we can build a release plan. As we make progress along the plan, I can measure completed work and project an actual release date. Without data, the best answer I can give is "soon-ish, I hope". I expect that the usability improvements won't be massive amounts of work. There are performance concerns we should look at. There may be a show-stopper bug that I want to either eliminate or prove nonexistent. Because the next version should address a lot of the labs feedback, I'd like to do at least one more labs release. We'd like to add some more statistics, so we can have clear indicators of the effect that FlaggedRevs has on en:wp. The major wildcard is patrolled revisions which are part of the current proposal; I'll learn more next week, but my hazy understanding is that will require a substantial amount of new work in the core. I'll post an update here at the end of next week or early the following week. William

On 12/10/2009 07:21 PM, Steve Bennett wrote: Great! We did too. To make sure that they're covered, have you posted them anywhere? E.g., here: http://flaggedrevs.labs.wikimedia.org/wiki/Talk:Main_Page If it looks like the upcoming work will be reasonably quick, then hopefully one push to labs will be enough. If it will take a while, then I'd like to release to labs at least monthly, so that progress is more transparent. And either way, although I'd like to ship to en:wp as soon as possible, I'd rather discover and resolve as many problems as possible in the labs context. No sense having millions of people tell us something dozens can. Thanks, William

"David Gerard" <dgerard(a)gmail.com> wrote in message news:fbad4e140912101314m6da7284fv4d149b3a362c667d@mail.gmail.com... Domas' concerns about hardware support are also illuminating ([1]). Has the switch to MySQL-5.1 alleviated those at all? --HM [1] - http://lists.wikimedia.org/pipermail/wikitech-l/2009-November/046001.html

2009/12/13 Domas Mituzas <midom.lists(a)gmail.com>om>: I hadn't realised hardware problems were in the way too ... Would it be possible for someone to write a techblog post about what's in the way of flagged revs on en:wp? Quite a few people are wondering what's up and why someone hasn't pulled the switch. - d.

On Sun, Dec 13, 2009 at 9:15 AM, Domas Mituzas <midom.lists(a)gmail.com>wrote;wrote: Well, your original post implied that lack of new hardware could hold things up. "Still, we need new hardware, and as long as it is procured and deployed, we'd be safe deploying FR." Are you saying this hardware is already procured and deployed? That it'll be procured and deployed before FR is ready? Something else?

On 12/13/2009 05:59 AM, David Gerard wrote: That seems like a fine thing to do. I've already promised to post an update here once we have a clearer picture; I'll write up a more general-audience version for the blog, too. William