-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hello, is it possible to commit translations to RHEL5 branch? Or any other? For most of the modules I see only HEAD or master branch which essentially means rawhide. Is it possible to update F8 translations for example and they will land on the user system after the package is updated (e.g. bug fixes).
Thanks.
On Sat, Mar 8, 2008 at 1:32 PM, Alexander Todorov atodorov@redhat.com wrote:
Hello, is it possible to commit translations to RHEL5 branch? Or any other? For most of the modules I see only HEAD or master branch which essentially means rawhide. Is it possible to update F8 translations for example and they will land on the user system after the package is updated (e.g. bug fixes).
Yup, it is possible (s-c-printer already does that). The reason why we don't have it for all branched modules is that we don't have a list of modules being branched and the status of each branch. We've been struggling to find these information so far.
Do we have a list of modules with RHEL5 branches actively being used to push translations/updates? In the stats the following are branched: anaconda, firstboot, pykickstart, initscripts, rhpl, rhpxl, s-c-kickstart, s-c-securitylevel. Looking at the VCSs, some POTs in that branch haven't been updated for a long time. Maybe we first need to make sure the PO/Ts are up2date and part of the build processs by the developers, so that our translators don't work on outdated stuff.
-d