One of the hardest things about doing the entire plugin development on my own is being able to do THOROUGH testing between each release. While I do have a dev box, a test box, and a live site that I install new releases on before "putting them out in the wild", I cannot possibly test all the features in the product.
The best way to iron out bugs it to have an ACTIVE beta test community. I even set up a mailing list for people to sign up and find out about beta releases. Nobody really reads it and I've NEVER had someone report a single bug from the beta test group.
This is where you come in. You can help test the plugin. To do so, please sign up for the my Beta Tester Mailing List at Mailchimp.
When a new MINOR release (3.X) or MAJOR release (X.something) is ready to ship I will publish "download the alpha/beta" links out on the list. This will be for all premium add-ons as well, which means this is a good way to play with a premium add-on for free. The only caveat is the Beta List gets a "close to final release" version not THE final release version as I almost always find something wrong that needs a patch before the final push.
Hopefully I get some active beta users soon. If not I will need to stop the beta program as it does take a good amount of extra work on each release.
How do I tell a good beta program? By issues reported on the Github issues list.