Hi Steve,

> In its current state?

Yes, that was the idea - none of those bugs that you are referring to were critical data-loss or crash type bugs...

But it may be better for me to focus on v2 as the target for that lite version in the future though, in addition to fixes other stuff like the much faster mesh output would work really well for someone who was focused on data conversion.


> to make a bug report, to then be told it is fixed in V2 and a
> need to upgrade to get a fix could not be taken well.

Well, v2 is certainly not perfect neither, no version will be. So this same kind of a thing could happen no matter which version I pick to fix for the "lite" version.

The only way around that would be to have the "lite" version be a kind of stripped down subset of the current actively developed version, rather than a frozen previous version.

However, producing multiple versions from a single active codebase adds some complexity and more work to my overall development process, so I don't really want to do that route.

- Michael