Description of problem: @32133 If I set my browser to German and go to CMS, I see inconsistent behavior. The main admin page is in German. However, if I click on an article, of which both a German & English version exist, I am dispatched to the english version. All the UI is in English. If I select the German version in the languages tab, I still see an English UI.
"However, if I click on an article, of which both a German & English version exist, I am dispatched to the english version." This is sort of by design. The DP merge has the section admin page show a list of primary instances, not a list of bundles. As to the second part, the locale of the UI being determined by the current item, that's wacky and I'm checking it out.
It turns out that item admin globalization is working fine, it's just that it's not currently localized. I added cms.ui.help=Hilfe (hope that's the right German) and the right thing happens when I set my browser to German. A slightly curious behavior of our g11n is that we fall back to English, not straight back to g11n keys, if say the German variant lacks a particular key. In summary, I don't think we have beta2 bugs here. We have an arguable misfeature (the browse tab shows primary instances rather than bundles that are subsequently resolved) and we have some incomplete l18n.
Retargeting for RC0 based on Justin's comment.