Hi all, The freeze that we were supposed to currently be in has been postponed. The reason is that we'd like to have Jo?o's version of BlueZ 5 A2DP support in the release, so that when we get BlueZ 5 A2DP bugs for PA 5.0, we don't have to debug the old BlueZ 5 A2DP code. The plan is to enter freeze as soon as Jo?o's patches have been merged. What does this mean for the release schedule? The previous plan was to release by 2013-08-16. That seems overly optimistic even if we didn't postpone the freeze. We will need to wait for Jo?o to finish the second version of his patch set, review it, possibly iterate more, fix the release blocker bugs, publish a release candidate, wait for feedback, and possibly fix more bugs and publish more release candidates. AFAIK, the date 2013-08-16 was chosen so that we would release before Gnome's freeze. It's not clear to me what the practical consequences are if we miss that date. Supposedly Gnome's interest in PA release schedule is that they need to test their BlueZ 5 code against a PA version that has BlueZ 5 support. Would it be enough if they did the testing against a git version of PA, or against a release candidate? The "decision" to postpone the freeze was done in an IRC discussion between me, Arun and Luiz. I'm still open to discussing it if someone feels that the new plan is bad. Finally, I'll repeat a thing that I've said in the past, but I've found that not everybody has noticed it: PA 5.0 will in any case have support only for A2DP when using BlueZ 5. Jo?o's patches are only refactoring/rewriting the BlueZ 5 A2DP code. HSP/HFP support in PulseAudio 5.0 will still require BlueZ 4. -- Tanu
