Thanks for getting back to my other post Vaska.
You say "We think our users prefer the way we solved problems" If you make it public on GIT or another repository, you still have control, allowing or disallowing commits (or is this what you meant by 'it is a lot of work' - to use a code repository?). So you can keep that problem solving style people like.
You said "there are reasons why it's not being developed in the open. There are reasons why we have waited so long." Please can you clarify? I'm genuinely just totally confused as to what is to gain by keeping development behind closed doors, and what is to loose by making it public. On the face of it it seems you are struggling to complete it with the spare time and / or resources you have but whatever the issue, some help would surely reduce your own workload?
People seem upset but I suspect its just the vagueness of a lot of messages / pages saying 'soon' that causes people problems - I understand if your still developing you can't give an end date, that's fair enough, but if you open or make transparent the process then this I feel would be avoided, even just giving some details, or having a controlled beta testing group.
On the forums its apparent there is a really strong community, so why not make use of it!?