On 2/19/13, Andrej Mitrovic <[email protected]> wrote: > I can see now there's a d.chm file in \bin.
Walter that .chm file you're distributing in Windows\bin is v2.058 (judging by the changelog), or some other version, but it definitely isn't the latest because documentation is missing (e.g. getProtection trait). Why can't we open up the release process so we know exactly which scripts and procedure is used to make a release .zip? That way we can catch these bugs in time.
