I do appreciate everyone's feedback to my original inquiry. To hopefully restate more clearly: my primary intent was to question why evolutionary B4J enhancements (including, again, some spurred by developer users' "wishes") - to its IDE, language compiler and various maintained libraries - are not regularly planned for implementation and deployment on at least a quarterly basis. In most software companies, deliverables are tied to product-specific feature roadmaps and typically deployed many times a year; typically via continuous [agile sprint-managed] releases.
If B4J was not a free Anywhere Software product offering, I'd expect something similar as a paid subscriber customer. And I'd gladly even pay a recurring annual license fee in order to get such frequent upgrades (along with identified bug fixes too, of course). Given that's not the case, it seems we all just have to accept that B4J may not evolve/mature much more now - or at least not on/per any known timeline or long-term plan.
That all said, and after 8+ years of personal use, I still find B4J a unique and highly effective cross-platform desktop application development environment as-is; and am quite grateful for its existence and amazing support (from Erel especially, and all the knowledgeable forum contributors here).