sfsailing wrote: Can you clarify something.
Why not run a dev server that is a mirror of your live sites to test this stuff on, and WAIT ONE WEEK before committing new code!
Thanks
I support this idea. For me personally I don't run ANY software on my live site without testing it on a test site. The reason is quite simple. I have been creating my content for years and don't want my mysql data damaged.
I've been testing this extension since beta1 (it was 6 beta releases), but I physically can't check everything (the functionality is too large to be easily checked)=>I can not be sure that everything is working fine.
The thing we are talking here is the payment extension with possibly thousands of records => thousands of clients=>their money, bank accounts, children...you name it
If this data is just disappeared due to a code bug I wouldn't want to explain all of them the reason why...
:
DTR is extremely serious extension, because it's related to MONEY
I think that support team should run the test site with open backend for everybody. Thus we can test it faster and check if it is really stable before running on real sites.
For now my project is between ground and heaven, because I'm not sure if I should create events in the 2.69 (seems to be stable), or wait until the stable 2.7 will come. Once the process of taking payments is launched it can't be stopped.
P.S. Also we need a member-only thread. Now all bugs are reported using tickets and I want to know what bugs are discovered by the others to be able to pay more attention on this on my site also. We need a kind of bugs log.
Yootheme team do this way and I swear I don't remember a bug in their stable versions.