We (DotNetNuke Corp) operate in a number of different teams - as well as the usual sales/marketing etc., the developers are split into support.maintenance, development (feature team) and community. These teams often have staff that float between them and the teams work together on releases e.g. support identifies issues which affect customers and gets those roadmapped, maintenance works on mainteance releases (and sometimes bugs in feature releases), feature team works on the 2 large releases (but also fixes bugs) and community works on community focussed efforts (such as Q&A, blog, forums etc.).
The community team "own" the forums module, and they've been the ones working on a 6.2.0 compatible release. This involves porting (and coverting to c# AFAIR) it, adding some additional features (i.e. copying features from the existing forums module that dont exist in AF Forums), testing migration scripts and adding integration for new 6.2.0 features (e.g. publishing moderation requests as notications, posting forum questions as journal entries). Obviously they needed 6.2.0 to be ready to finish some of these, and unfortunately some changes between beta2 and the RC of 6.2.0 (mainly API reorganisation of service framework requests) has meant they had to re-do some of the 6.2.0 integration. So far, they've pushed out an updated blog module to dotnetnuke.com (and are fixing some minor UI/UX issues), have pushed an update to the Q&A (exchange) module and are currently helping us with some load issues (the member directory module is having some trouble dealing with the million+ users on dotnetnuke.com). My understanding is that when those items are stabilised that the forums module will be next, with it first being upgraded on dotnetnuke.com, then a period of stabilisation, and then the final release will be pushed to codeplex for all to enjoy.
Note: as should be clear we did not push back forums as we're working on social - they're 2 different teams with 2 different workloads.