RE: Understanding the branches



Dear Rafael,

 

Thank you for detailed message! I just want to make sure all Tajik translation are committed correctly, so we do not miss a word for the next release.

I will continue to commit translations to "master" only and to a 'gnome-3-10' git branch if information about it available on the Damned Lies.

 

Kind regards,

Victor

 

 

From: Rafael Ferreira [mailto:rafael f f1 gmail com]
Sent: 18 сентябр 2013 с. 19:31
To: Victor Ibragimov
Cc: Piotr Drąg; gnome-i18n
Subject: Re: Understanding the branches

 

I believe it is interesting to commit to 'gnome-3-10' git branch (always with cherry-pick to 'master') in the situations of GNOME 3.10 is not release yet or minor releases (e.g. 3.10.1) are to be released.

 

As you mentioned, some modules doesn't have a 'gnome-3-10' git branch. I'm not sure why, but, for you as a translator/coordinator, it means that you have to commit to 'master' only.

 

There are other exceptions that have different names of git branch. Gtk+, for example, have git branch names like 'gtk-3-8'.

 

Releated to your question, yes. You should translate branches available in Damned Lies. On the other side, If Damned Lies don't show a 'gnome-3-10' git branch, this git branch is probably not ready for translators or doesn't even exist.

 

 

 

2013/9/18 Victor Ibragimov <victor ibragimov gmail com>

"gnome-online-accounts", "gnome-photos" and "gnome-terminal" committed to both master and gnome-3-10. And it seems to be that "gnome-3-10" is not yet available for all modules.

When you suggest to commit to both "master" and "gnome-3-10" do you mean that is possible to commit to both branches just when "gnome-3-10" is shown under the "Branch" on Damned Lies site as a reference?

 

Victor

 

From: Rafael Ferreira [mailto:rafael f f1 gmail com]
Sent: 17 сентябр 2013 с. 20:43
To: Victor Ibragimov
Cc: Piotr Drąg; gnome-i18n
Subject: Re: Understanding the branches

 

 

 

2013/9/17 Victor Ibragimov <victor ibragimov gmail com>

Regarding the branches or to make sure I correctly understand the branches:

What is the difference between the master and development (for example, GNOME 3.10 (development)), and old stable?
If translations or updates are committed to gnome-3-6 now - is this a waste of time, as gnome-3-6 will not be released anymore?
What if translations and updates are committed only to gnome-3-10? or/and only to master? or why to commit to both gnome-3-10 and master?

Thank you,
Victor

 

A 'gnome-3-10'  git branch is planned to be released together with GNOME 3.10. The 'master' is the latest git branch ever of a module - every future new branch will be forked from 'master' (e.g. 'gnome-3-12' would be a fork of 'master').

 

Commiting translations to gnome-3-6 is waste of time at the moment, because a commit would only be of any of use if the software will have a new release. So, for example, Gtk+ 3.6.0 won't be releasing another minor version adn therefore it wouldn't make sense wasting translation effort on it. Obsolete, in resume.

 

Commit translations only to 'master' and not to 'gnome-3-10' will result in your translation NOT being available in GNOME 3.10 -- which I think is not a good idea. Commit translations only to 'gnome-3-10' and not to 'master' will result in the translations being available in GNOME 3.10, however your lastest ever translation state will be out-of-dated -- your effort in GNOME 3.10 wouldn't be available in GNOME 3.12, for example.

 

So, best you can do right now (close to a new GNOME release) is to commit to 'gnome-3-10' git branch and, then, run a git cherry-pick (more information in the URL mentioned by Piotr).

 

Cheers,

Rafael Ferreira

 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]