From: "Thomas Roswall" <[EMAIL PROTECTED]>
Date: Sun, 12 Nov 2006 14:16:46 +0100 (CET)
Hi,
> would this now correspond to the OOE680_m2 or the SRC680_m193 build
> from pavel, or neither of them? or will we have another category set
> up in the TCM-tool
localisation17 corresponds to SRC680m189 with your GSI file (downloaded in
some point in the past) merged in.
Pavel's OOE680_m2 corresponds to OOE680_m2 with your up-to-date GSI file
(downloaded minutes before the build starts) merged in.
Pavel's SRC680_m193 corresponds to SRC680_m193 with your up-to-date GSI
file (downloaded minutes before the build starts) merged in.
So: if you stopped changing your GSI file at the moment when you filed an
issue for Ivo to merge it in, my build has the same strings as
localisation17, but is based on newer milestone.
If you continue to update your GSI file, my build contains newer
translation and is based on newer milestone.
> So it depends if you want to test translations going to be merged into
> the master or translations on the way to the final version you'll
> use. But I think the differences are so minor, that it does not
> matter ;-)"
What matters here is to test if the merge process was OK. This is the
reason to test localisation17 builds, because they represent the actual
merge that will be done in the CVS, into official source tree.
My builds, on the other hand, will not use translation from the official
source/CVS because they are "old" for many translators who continue on
updating them after they filed and issue to merge it in and before the
actual release. In this time, they do a lot of bugfixing, so they want to
have their newer version merged in.
--
Pavel Janík
Don't stop with your first draft.
-- The Elements of Programming Style (Kernighan & Plaugher)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
