Hey, everyone!

I'm about to roll out a new version of Dada Mail, which has almost nothing but bug fixes, some embarrassingly obvious to anyone who uses Dada Mail In a strange twist of behavior, those are sometimes the hardest bugs for me to see, just because I use Dada Mail in most unusual ways (being the guy that makes the stuff)

I've been getting some great feedback as of late of bugs in the program from users on this list, on the boards and via github, so thanks a lot! Many of the bugs I personally file are from users that have problems with a feature of Dada Mail that I investigate, find that it's a bug and then patch in a future release I would say a good majority of my development time is doing this Works pretty conveniently, given my position No complaints :)

One of the things that would be more useful is if I got bug reports on development versions, of which I get almost nothing (sad face), so when I ship, I always don't know if I've just been lucky with my changes in my limited test environments, or if there's still problems with a closed bug/new feature

Can you think of anything else I can do that may encourage more reporting in the development versions? At the moment we have:

• an open repo via github

  http://github com/justingit/dada-mail/

That anyone can download a copy of a dev version of Dada Mail at any point of its development and try stuff out You can also fork a copy of Dada Mail and work on anything you want and request that I, "pull" the changes back - there's even a way to edit the files on the github site, without the need for any other steps/apps/workflow to learn, etc

• I also release snapshots of alpha/betas/release candidates to help us all be on the same page

• I update the changelog and post it with any release announcements

• There's the test suite that you can run with one simple command, to make sure everything that has coverage works with your specific environment

• And well, there's this discussion list

Is there anything else I can do to help everyone?