[Kde-pim] Re: 4.7 branch

[Albert Astals Cid]

A Thursday, June 23, 2011, Torgny Nyblom va escriure:
> > A Thursday, June 23, 2011, Burkhard Lück va escriure:
> >> Am Donnerstag, 23. Juni 2011, um 08:25:51 schrieb Torgny Nyblom:
> >> > > Am Donnerstag, 23. Juni 2011, um 03:28:15 schrieb Allen Winter:
> >> > >> On Wednesday 22 June 2011 2:57:24 PM Torgny Nyblom wrote:
> >> > [...]
> >> > 
> >> > >> *  the 4.7 branch is closed for anything other than bugfixes with
> >> 
> >> no
> >> 
> >> > >> i18n
> >> > >> changes without permission.
> >> > > 
> >> > > Scripty still tracks kdepim-runtime, kdepimlibs and kdepim master
> >> 
> >> for
> >> 
> >> > > gui and
> >> > > documentation messages.
> >> > > 
> >> > > As long as this is not switched to 4.7, master is in string freeze.
> >> > 
> >> > This is a setting on projects.kde.org, is that honored and if so does
> >> 
> >> it
> >> 
> >> > need coordination when switching?
> >> 
> >> Sure, if you simply create a 4.7 branch for kdepim* without coordinating
> >> this with kde-i18n-doc, string freeze rules still apply for master and
> >> 4.6.
> >> 
> >> Scripty has only two branches for KDE main modules, master/trunk
> >> (trunk/l10n- kde4) + stable (branches/stable/l10n-kde4).
> >> 
> >> Gui + Doc messages from KDE master are tracked to trunk/l10n-kde4 ->
> >> translations for upcoming 4.7.0 -> master is in string freeze
> >> 
> >> Gui + Doc messages from KDE branches 4.6 are tracked to
> >> branches/stable/l10n- kde4 -> translations for upcoming 4.6.x ->
> >> branches
> >> 4.6 is in string freeze
> >> 
> >> CC-ing our I18n Coordinator Albert Astals Cid.
> > 
> > Burkhard is right, until after 4.6.5 is released stable l10n will track
> > 4.6
> > branches and trunk l10n will track 4.7
> 
> If we switch the "trunk" translations to the 4.7 branch then master will
> be open for new/changed strings, or?

You can do any commit you want on master already (well i don't know what the 
general schedule says about it, but regarding translations it is fine)

> If we do this switch do that need to be coordinated or will it "just work"?

Sadly things never "just work". The truth is that as maintainers are reckless 
regarding the definition of their i18n branches, the branch used by scripty is 
decided by a list in the l10n scripts and by the definition in 
projects.kde.org. When you change the definition in projects.kde.org the only 
thing that will happen is scripty giving us a warning that its definition and 
projects.kde.org one does not match.

Albert

> 
> /Regards
> Torgny
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/