All feedback, reports, suggestions etc. count, not only bug reports. If you tested many tools and wrote a brief report on what tools you did test and how they performed that would also entitle you for a free license.
The point is that you must somehow
1) show that you have actually done something, and
2) provide some information that is useful in the context of beta testing.
OK, so I know where I stand - this may sound like sour grapes but I assure you it isn't. I went out of my way to test the product (for your benefit, not mine) and because I found nothing wrong AND reported such and spent my time ... etc, etc the thanks I get is for you so effectively say - tough!
I did show I'd done something. I spent time here reading bug reports and trying to reproduce - are you seriously telling me you wanted a lot of AOL responses saying "/me too" to somebody posting a note that says Release x.y.z.1.2.3 is fine? Come on be serious.
How did I show - I made a post or two here and sent eMails .... but I guess that isn't enough so that's your call. Still it'll guaranteee you a smaller beta test base next time and that'll lead to the inevitable missed bugs, follow ups, fixes, etc.
If you want to limit the number of free licenses then either go for a fixed number of beta testers (say 200 or whatever figure grabs you) or state from the outset that only the top 50 guaranteed bug reporters will get said license.
It's not rocket science old bean.
Oh and FWIW - I do like the product, I just don't need to utilise it myself but felt one professional to another you'd appreciate the extra input ... c'est la vie.
