No verdict. I'm just hoping to make it to the new year and a solid 2.0 release.

Actually, I did have one related thought... trying to determine the purpose for inclusion of something like this. Rules is nearing a full Drupal scripting language/engine. In Ubercart, we wanted a solution that allows folks who aren't programmers to come in and fiddle with some conditions on normal workflow actions (customer completes checkout, payment gets entered, etc.) and checkout decisions (like which tax to apply and which shipping quotes to offer). The complexity of Rules is great, but is it too much?

I haven't decided, but I'd entertain feedback on the question. Basically, I don't think 95% of our users need something as large as Rules provides, and those who do would be better off writing custom code that hooks into the Uber-API. I'm not belittling Rules at all, and frankly I'm incredibly impressed by the features it provides. I just think our target audience for the UI based conditions system is broader and less technically-inclined.

So I'd almost call for a two pronged approach of seeing how we can simplify even more what is offered in core and tightening up the core APIs and documentation so they're accessible to more developers. Perhaps the "third" prong could be a UC Rules module maintained by folks who are more interested in using Rules with Ubercart.

Thoughts?