Regenerate all po files to bring up to date with cpython 3.13 #607
Conversation
|
Like the other day, I'll mostly trust that this has gone as expected. One question only: Should we maybe wait to update with the commit that'll become the 3.14.0b1 release? Also, after this is merged, we should update the default branch and change the base for all open PRs. |
|
I agree that we shouldn't wait. As soon as we start the translation based on 3.12 and as Python releases new versions, we can maintain the docs accordingly. This means that when 3.14.0b1 is released, we can add a new branch for this version while continuing to support 3.12 and 3.13. Additionally, I believe the best approach is to focus our efforts on translating 3.12 first. When we will have make a small progress we can efficiently transfer thoses translations to newer vesions like 3.13 and 3.14.0b1. Regarding the branch strategy, I suggest keeping the 3.12 as the default branch for now. However for the short future I suggest having a default branch as a 'master', dedicated to overall project documenation like README and contribution guidelines. This branch will guide contributors with the clear milestone of translating 3.12 files, with future version updates building on this foundation. |
There was a problem hiding this comment.
We synced offline with @skpanagiotis and figured out a branching plan for the future. Let's get this in so that we can start working on 3.13 and hopefully get the translation into the upstream language picker.
.pofiles withmake merge.Makefilewith new cpython commit hash of3.13