Git migration
Karl Ove Hufthammer
karl at huftis.org
Thu Apr 3 20:46:02 BST 2025
Emir SARI skreiv 03.04.2025 21:35:
>> I have now uploaded the Git repositories for*all* languages to
>> https://invent.kde.org/users/huftis/projects
>> so that you can test them.
> Has anyone found time to test Lokalize with the new repos? What would be the ideal way to handle it from now on, two separate projects for 5 and 6, or would it be possible to sync these branches through one project?
You can use the normal sync feature in Lokalize, just like before. But
this only supports a single sync/branch folder, so you would need a
separate project for either 5 vs. 6, or for trunk vs. stable. And it
doesn’t support files that have different names in 5 vs. 6 or trunk vs.
stable.
As always, the easiest way to handle all branches at the same time is to
migrate to the summit workflow.
> Also how about the templates? We will need to clone it separately, right?
Yes. They are here: https://invent.kde.org/huftis/kde-l10n-templates
> Some sort of “ideal” beginner workflow type of thing would be nice to have.
We will provide a simple SVN-to-Git migration document listing the
changes from SVN to Git. But the translation workflow will basically be
as before, with no major changes.
--
Karl Ove Hufthammer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20250403/13a75639/attachment.htm>
More information about the kde-i18n-doc
mailing list