Hi,

In understand both opinion of Ryan and Fago

I just would add that, even if the workflow integration brings some unwanted step for configuration (example shipping : You add the shipping quote, and then, you activate the workflow rules and define the conditions). Workflow allowed to define some usefull and complex conditions/actions without coding one single line.

I wonder, if Ubercart get rid of Workflow/rules, if it will be able to provide all the possibilities workflow already provide. Some workflow conditions and actions, not specially related to ubercart are very usefull. For example, get the user role to calculate a tax rate etc...

In addition, a lot of modules began to integrate workflow-ng, they all add some new actions, conditions, without the need for ubercart to add a single line of code. Example the organic group or nodeprofile integration, I don't use them with ubercart ATM, but it could be usefull for people to create a relation between a group and ubercart, and workflow is a good gateway for that.

If ubercart begin to write his own solution, this would involve that these module have to write one more integration to beeing usable with ubercart or ubercart to write extra code to beeing usable with these modules.

EDIT : I would like that, more than workflow, there is another dependencies/integration that it would be judicious to remove, it's the imagefield integration. This module took too much time to go out, and the issue queue for 6.x pratically seems dead. A very good alternative, more more reactive grown up, it's filefield with filefield image.