There is also
https://bugs.eclipse.org/bugs/show_bug.cgi?id=570189 which popped up. It's not a blocker per se and issue has been existing for a looong time; but it has revealed as consuming a lot of energy lately. As much as I'd like to get it fixed in next release, I think it's also too intrustive, difficult and risky task to guarantee a good fix in a short time frame; and we'd lack time to properly test it before release. So I suggest we just skip it for 2.2 and make it a higher-priority item for 2.3 (hopefully fixing it early so we get plenty time to use the snapshots). Thoughts?
Such a change would need month+ for proper testing with various projects so not 2.2 content IMHO.
Is there anything left to wait for? Without answer, I'll start the staging process on Monday, to hopefully complete the release on next Monday. If anyone is interested in taking care of the staging/promotion process; just ask and I'll gladly let you do it and assist.
