@julen Several of your last PRs were really simple changes. Perhaps you have good reason to PR those, but if not next time perhaps it is better if you directly land them to master. Not that I am against of reviewing changes that land on master, but better focus on the ones that do require actual peer review.
hi @unho, sure, that makes perfect sense to me and thanks for bringing that up. If you need any reasons, in these particular PRs I wanted to raise a heads-up on the test changes as they outline an existing problem, and in reports-related stuff just wanted to have the original coder's blessing
@/all suggestion's stuff is our priority and we'd like to deliver important changes to our clients asap. We have discussed translate/pootle#4630 which is addressed in translate/pootle#4635. So I'm going to land it if there are no objections.
@unho why have you put feature/suggestions tag to translate/pootle#4622?