2.5 months, anything new?

[alectron22]

@LarsBjerregaard

Focus on getting V2 out the door before the VST version.

There was a release plan here with a rough roadmap:

Rack development blog

The tentative release plan for Rack v2 and Rack for DAWs is the following. By “wait”, I mean “ensure that a certain amount of time passes before the next step”. Continue working on Rack v2 and Rack for DAWs. Once both are “alpha” quality, release Rack v2 source code. Wait at least 4 weeks while testers and plugin developers review the code. Once both are “beta” quality, begin providing development builds of Rack v2. Send Rack for DAWs builds and licenses to testers. Wait at least 2 weeks for u…

But - complex software dev is never an exact science, and health/wellbeing and enjoying VCV (i.e. the great thing Andrew and the community already have built) are much more important than sticking to loose, old plans). And to achieve those in the long run, it might also be necessary to take more time out, or get help for certain areas - but that only Andrew and those involved closely can judge.

But, Fingers crossed the v2/VST release generates enough income for multiple people, so Andrew could employ friends/colleagues/community members to potentially take over the areas/parts that cause the biggest emotional/mental drain (i.e. I’d assume managing community communication & expectation management & the occasionally occurring drama around it play a large role when a project becomes as loved & successfull as VCV and can be difficult to deal with for everyone, on top of the technical challenges that VCV v2 & VST hold).

Thanks for the open words @Vortico in the dev blog - and I wish you all the best, and if there’s anything I/we can do to help, please don’t hesitate to reach out!

c.