How to deal with numerous immediate bugs in Plone 5

IMHO, you have a reasonable concern. If we are going to ask to test alpha versions of things, we ought to have some process to release nightly builds that work with unified installer?

Since we do not, I think it should be a fine shortcut to submit translation bugs, if:

  1. You see them in currently released Plone 5.0.6, and...

  2. You compare the .po files to master branches on github, to see if anyone actually tried addressing this in 5.1. That is easy enough in a browser:
    a. Determine package the .po file in question lives in locally (in your eggs directory);
    b. Go to${PACKAGENAME} to browse source, and find the .po file on the same relative path as it exists inside the egg distribution for the same package.