<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/21 Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello translator and release team friends, as you may know 4.12 is very close<br>
to its beta release and that brings us an interesting problem.<br>
<br>
This is the problem:<br>
October 31: 4.11.3 tagging<br>
November 6: 4.12 Beta 1 tagging<br>
November 13: 4.12 Beta 2 tagging<br>
November 20: 4.12 Beta 3 tagging<br>
November 27: 4.12 Release Candidate tagging<br>
November 28: 4.11.4 tagging<br>
December 11: 4.12 tagging<br>
January 2: 4.11.5 tagging<br>
<br>
<br>
As you can see only a week after 4.11.3 we have the tagging of 4.12Beta1 and<br>
then a lot of beta/RC releases of 4.12 with the final release of 4.12.x in<br>
between 4.11.4 and 4.11.5.<br>
<br>
That is all fine code wise since we have an infinite number of branches, so we<br>
basically have KDE/4.11, KDE/4.12 and master and people just fix stuff in the<br>
correct place.<br>
<br>
Translation wise it is a different, we only have two branches at a time,<br>
stable and trunk, so mapping those three branches is going to mean doing some<br>
compromises in what code branch ends up in which translation branch.<br>
<br>
This is my suggestion:<br>
* Before KDE SC 4.11.3 all is like now, stable-l10n points to KDE/4.11 and<br>
trunk-l10n points to master<br>
* After KDE SC 4.11.3 and before 4.12 Beta 1 we make stable-l10n point to<br>
KDE/4.12 and trunk-l10n points to master<br>
<br>
This means that for KDE SC 4.11.4 and KDE SC 4.11.5 we will repackage the same<br>
translations of 4.11.3 (actually we'll package them from<br>
<a href="http://websvn.kde.org/branches/KDE/4.11/kde-l10n/" target="_blank">http://websvn.kde.org/branches/KDE/4.11/kde-l10n/</a> but since that's outside the<br>
l10n workflow i don't expect people to touch it much/at all).<br>
<br>
Comments?<br>
<br>
Cheers,<br>
Albert<br>
</blockquote></div><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Sorry, I may not be very into position, but I have a question: Why do release team wants to keep releasing 4.11.5 on January 2014 when 4.12 is out on, according to release schedule, Dec. 18 2013?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Franklin</div></div>