This module needs a little direction to make it more powerful and stable, I'm dropping here a quick roadmap to put commerce coupons in shape, feel free to comment other areas of action that you think are required.
Basically I consider we need three areas of action:
- "Standarize" our code, as I've seen commerce coupons is using is own way to do things, one big example is the entity management, I've made a little step in this issue , but we need to base our entities in Commerce core ones asap.
- Move not 'Coupons core' stuff out of the module, say it drop ballast if you want, I've proposed to move feeds integration into commerce feeds here but I think it would be clever to move the batch and basic modules out of here, to its own projects. I'd take batch one i.e., and probably alex would like to get basic himself . New modules would have its own space. This would force us to make coupon API stronger and more stable and we'll make this more neat and sustainable.
- Squash major & critical, we have as now 10+ issues just marked in status that consider the module "unusable" but the total count of issues is 62 for a 441 uses module. That's bad.
I think it could be also a good thing to review googletorp's version of the module, see
Let me know what you think, I'll start addressing these as soon as my co-maintainership is accepted
I don't feel we need to make a 2.x branch as the 1.x branch is not operative enough to keep it and I don't see as now we need to do any mayor database moves.