This PR pulls the recent translations from the Transifex.com using the bitcoin-maintainer-tools/update-translations.py tool.
According to our Release Process docs, it is supposed to be merged before v26.0rc1 tagging.
This PR pulls the recent translations from the Transifex.com using the bitcoin-maintainer-tools/update-translations.py tool.
According to our Release Process docs, it is supposed to be merged before v26.0rc1 tagging.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | stickies-v |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
ACK 74604662f33fe73ac4f2c707b467272795ccecdf
Verified that I'm getting the same results after running bitcoin-maintainer-tools/update-translations.py on df28880ec050b732e6f6402f6afc53a052591ee7 (current 26.x tag). I did not inspect the translation results themselves.
According to our Release Process docs, it is supposed to be merged before v26.0rc1 tagging.
I think the release process docs need to be made more clear, because they say this was meant to be done before branch-off?
https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-branch-off Translations on Transifex: Pull translations from Transifex into the master branch.