Hello,
our localization system, for every single doc component is broken.
The reason is the change of branch from "master" to "main".
While I don't mind about the name given to the default branch, I'm not comfortable of loosing language support because of this.
I tried this to make it work: https://pagure.io/fedora-docs/translations-scripts/c/f5f541f2f46c36559ed4a6a...
the question I have: how could we have better testing of changes?
Thanks for your understanding,
Jean-Baptiste
Hi Jean-Baptiste,
On 12/8/20 6:06 PM, Jean-Baptiste wrote:
Hello,
our localization system, for every single doc component is broken.
The reason is the change of branch from "master" to "main".
I do not understand how this happened. Only a handful of Fedora Docs repos have switched from `master` to `main`. Did the changing of a few repos have an impact on the translations build script? If so, which repos specifically caused localization to break?
the question I have: how could we have better testing of changes?
Thanks for your understanding,
I am still confused how it happened. If any docs repo can break the localization tooling by changing the default branch, this seems like a bug with the tooling. Right now, no mass branch renames have happened yet, although this is planned in the near future:
https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main
Le 09/12/2020 à 18:24, Justin W. Flory a écrit :
the question I have: how could we have better testing of changes?
Thanks for your understanding,
I am still confused how it happened. If any docs repo can break the localization tooling by changing the default branch, this seems like a bug with the tooling.
Bugs occurs all the time, no need to argue on why a bug occurs, the real question is: how could have better testing of changes?
Right now, no mass branch renames have happened yet, although this is planned in the near future:
https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main
Interesting, how do project list themselves for automatic transition?
Jean-Baptiste