Community
Participate
Working Groups
Currently, all usage driven documentation is grouped by type and method names only. If there are differences between, say, a type in version 2.0 and 3.8 there are no means to express that. This should be addressed til Juno.
With M6 the extended documentation platform uses the same maven-based backend as call completion. As such, it's now version agnostic.
Set target milestone for fixed bugs to 1.0