It's a bit unfair when beta-testers knows what planned in future and people who coding does not know what to wait. VCMP needs to be more opened in this aspect.
Not really. The concept of limited beta testing has more or less fallen by the wayside since the devs could make changes, test them internally, push them to the public, and then immediately push bugfixes if we failed to catch something. We could definitely make use of an active beta testing team to better polish our releases though.
Even then there hasn't been anything terribly exciting to report. The past week has been spent upgrading our web servers' operating systems, the forum software, the wiki, etc. and making sure that we can still SSH into them. This is why some people might've noticed the forum, update server, masterlist and such intermittently going offline.
As far as transparency goes:
- We have a bug tracker that I've been using for tracking issues for releases.
- I have a crude server plugin for writing scripts in .NET (so C#, VB.NET, etc.) on my Bitbucket profile that I've been making very small incremental changes to. It's extremely incomplete right now; I originally started writing it a long time ago for Argonath but got stuck on a server crash that would regularly occur, which got fixed only very recently.