11.07.2015 22:24, Mattias Gaertner пишет:
On Sat, 11 Jul 2015 20:05:36 +0200
Péter Gábor <[email protected]> wrote:
Today I noticed that a new release of Lazarus is prepared (time of last
update on sf.net 'Files' page is newer than the release time of listed
files).
Yes, 1.4.2. It is a bug fix release. No new features.
[...]
So where can we know that we can upload the translations without missing
future changes?
A true release model with strict phases (including "frozen source
strings" at last, maybe two weeks) would be very useful.
The 'fixes' branch only contains bug fixes. So almost all
changes to resourcestrings are either fixing typos of the English
version or add new error messages.
Yes, most of translations changes are string additions, i.e. some string
in interface was untranslatable before and then resource string got
added for it. This doesn't cause translation regressions.
Sometimes some strings get changed though, but such changes are quite rare.
Waiting a week means translators and maintainers must work with an
additional branch.
I'm not sure if it is worth the hassle. Maybe Maxim who applies the
biggest part of the translations can tell.
I agree here, there is not so much translations changes in fixes branch
anyway.
BTW, in case of 1.4.2 release the LAST merge affecting resource strings
was done a MONTH AGO, on June 11.
I would recommend translators to send translation updates for FIXES
branch as soon as they have them at hand. For trunk it is enough to send
them once a week.
--
Best regards,
Maxim Ganetsky mailto:[email protected]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
