Closed (fixed)
Project:
Commerce Authorize.Net
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2012 at 16:42 UTC
Updated:
12 Oct 2012 at 01:31 UTC
It would be nice to have a stable release to provide site builders more certainty that the module will get an SA for any security issues. Please feel free to update this issue summary to include links to issues to fix prior to that release.
As of this post, there are no critical bugs in the queue.
You can use the tag D7 stable release blocker to help others identify issues that are blocking a stable release. Currently there are no issues with that tag.
Comments
Comment #1
rickmanelius commentedBump
Given the following:
- There are already 992 active installations of this module in dev format.
- This module doesn't provide DPM/SIM, therefore these installations are potentially at risk for PCI reasons.
- There are still a ton of D6 and D7 ubercart users out there (44,000+ as per the project page), and most of them probably can't make the move until there is a reliable gateway available.
This would seem to be to be a priority. Jumping in the issue queues to see if I can help. I'll try to mark any major/critical tickets in here to try and get this ball rolling.
Comment #2
rickmanelius commentedHaving reviewed all 32 open issues, I feel the only 2 issues I'd consider 'release blockers' would be the following:
#1328762: Credit card rejected/declined, order goes through anyway
#1759062: Billing address must preceed the payment method
Everything else appears to be a feature request, a minor bug, or a support request/question. Therefore I propose that this module push for a stable release after these issues are resolved.
Thank you and good night :)
Comment #3
gregglesIMO, a beta could be created now and 1.0 after those issues are fixed.
Comment #4
rickmanelius commentedI can get behind that. I'll try and ping rszrama and see what his thoughts are.
Comment #5
rszrama commentedDone. No more bugs and pending patches were committed for the most part, with the exceptions being related to sending more verbose API requests. Will add those in for the full release; they seemed to need a bit more work / testing.