So first, we're not going anywhere. We've hired a handful of people in the last couple months alone. We're a sub-100 person company, for reference). Our presense at Oshkosh will be expanded from the last couple years, which itself was an expansion over our previous indoor-only booth.
But we agree that we're not meeting your expecations here. We try to be communicative enough without getting too "inside baseball". It's a balance, and sometimes we don't nail it - especially for you guys (the forum contains - by far - the highest concentration of passionate Dynon pilots).
Historically, we've actually had some smaller "point releases" where we've occasionally deferred documenting smaller features until the next bigger feature release. These go relatively smoothly because we don't draw attention to them with notices on our site about upcoming documentation, and we try to limit those features that we defer to those that affect a relatively small population or that we think are otherwise fairly self-documenting. A litmus test is "if we're getting a lot of calls/inquiries about ANY feature that we can answer better in documentation, it's not adequately documented". That really applies to features that have already been documented too. Anyway, so with the latest point releases, we made sure to have the -472 documented, because it affects all installations going forward. But we deferred on some other more incremental updates.
Two things conspired to to throw off our normal rhythm, where we publish with software releases. First, we've changed the way we develop and deploy software. This is more about team organization, not actual code, and I'll leave this here. And second, we went through some both expected and unexpcted personell changes in our support team that left us a bit light in some areas. Documentation production happens between a few different areas at Dynon, and right now those resources are helping our new support staff get up to speed and help them to continue to provide the expert support we're known for. Incidentally, our technical support is now 100% staffed by pilots. Both of our newer hires are A&Ps, and one is an IA too. We think you'll like talking to both Garrett and Rick.
Anyway, that's not an excuse, but that's what's going on. I don't have a date to promise on the documentation availability, but it's a priority for us.
