Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Bruce Hill wrote: > I like John's suggestion from below. Me too... it's been suggested by a couple of people now. > I'd suggest posting a request for additional testing when > a development release is nearly ready to become a stable release, > and wait for a month with no major or critical bugs before making > it the next stable release. A month might be too long for me to keep my itchy fingers off the keyboard :-) I'm hoping there's a reasonable number of people using the bleeding edge version, so I'm aware of problems early on. For example with the current release it's been through hell, so I'm pretty certain it's OK. There won't just be a single stable release, so even if something gets missed I can fix it and put out a new release when required... with that in mind I reckon a week or two is OK (if I say a clear week after the last critical/major bug report then that seems about right). Improving the test scripts is needed too - the one I have now works for the major functions but I need something a bit more complex... Something like the sanity.sh but without the insanity! I know what I want a test script to do... it's just a matter of writing it. Now is a good time as I edge towards a stable release (2.0.0!) Tony