According to the VideoLan official roadmap (
here), v3.0.0 is 5 weeks late, 98% complete, and has 7 active tickets that are blocking the release.
It's hard to predict how much longer until VLC 3.0 stable is released, though since they are on Release Candidate 8, it sure feels like it is close.
My plan is that once v3 is released stable, I will implement it, though I may start working with the release candidates as the blockers don't appear to be anything that would affect my coding of support.
I can't tell how complete the documentation is for 3.0 - a lack of proper documentation might make it too hard to implement in the current state, so no promises at this time. If documentation is a problem, I may have to wait for it to catch up.
I have no plans to code for pre-v3, since in a few weeks time those versions will be obsolete. Do note that I am open to changing my mind about pre-3.0 support if v3 turns out to be problematic for MM Browser users.
It might also turn out that VLC 2.2 is functionally equivalent as v3, at least as far as integrating with MM Browser, so there is the possibility that by adding v3 support, I also happen to add older version support. No idea, really, but that would be lucky if it is the case.
Have you done any testing with V3? I would be interested to hear your feedback, is v3 worth waiting for or are there new problems with it that make v2.2 a better choice?
Paul