Hello koha-devel, Some months ago, Frederic started an interesting thread about translations and their consequences on the git repository size. The wiki page speaking of this is on http://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking
We have decided nothing and only a few of us have expressed their opinion. Now, there is a big patch from Ukraine, that add another 2MB to Koha repo size (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6434) Frederic proposes 3 scenarios: 1- Keep history -- Create two (or more) Koha sub-projects, one for Koha code koha-core, and one for Koha .po files koha-i18n, and keep the whole history in both of the repositories. 2- Keep history as history -- We froze the current Git repository in which Koha history will live for eternity as a koha-legacy repo, and initialize two new clean and fresh repositories. 3- Keep-loose history -- Keep the history in koha-core, start fresh for koha-l8n. The gain is impressive (see: http://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking#Evaluation) When Frederic wrote the page, the repository was 177MB large. Now, it is 355 ! I think we can't continue that way, and should decide something before 3.8 is released (in 3 weeks) Everyone is welcomed to read the wiki page, express his opinion, I propose to have a vote on the next IRC meeting. Frederic = isn't there another option ? = a huge "git rebase -i" where we would discard all commits that are related to .po files (the list being found with git log --oneline misc/translator/po (i haven't checked it work, just rising the idea) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
