--nextPart16977894.lpF5TMN6fg
Content-Type: text/plain;
  charset="gbk"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Alle 10:40, marted=A8=AC 14 giugno 2005, Stephan Kulow ha scritto:
> Am Dienstag 14 Juni 2005 07:53 schrieb Funda Wang:
> > I know that it is suggested that extragear modules maintainers should
> > keep trunk version somewhere
> > else. But would it be very difficult adding those modules into stable?
>
> There are some problems connected to it, but we're working on it.

I'd like to mention one issue about extragear files in stable. In our=20
translator group we are quite dependent on our own database to assign=20
responsibilities to files (who has to/can translate what). Our system is=20
designed such as to point even the most clueless translator to the correct=
=20
file in WebSVN, to avoid problems related to technical misunderstandings (i=
f=20
we were to expect every translator to be confident with SVN, we would not=20
have that many).

However, until now we have been working only with branches applied to entir=
e=20
packages (kdeadmin, kdeutils...), and our system has been built around that=
=2E=20
=46ollowing two branching subjects (main kde packages and koffice) is easy,=
 but=20
following each extragear file is probably going to be error-prone.

I was therefore wondering whether you could cram in the stable branching of=
=20
extragear some sort of machine-readable way of finding out whether an=20
extragear file is in stable or in trunk. For instance, a simple text file=20
(say, "extragear-stable") to be left on the Internet, or even better in=20
Subversion itself, possibly maintained directly by the extragear group,=20
containing a simple list of which files are to be considered in stable=20
branch.

extragear-stable
=2D------------------------------------
messages/extragear-office/kile.po
docmessages/extragear-office/kile.po
messages/extragear-graphics/kst.po
(etc.)

In practice what we would need would be a simple way to find out what we ha=
ve=20
to translate in the extragear.

Cheers,
=2DFederico

--nextPart16977894.lpF5TMN6fg
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCrqson7A1uidpHYMRAs0YAJ92tL0Gj7Boce5G5zg+/W8uzBQnKwCfTDiX
MKOgphfFDsKkoFeOnLknIbM=
=pYOe
-----END PGP SIGNATURE-----

--nextPart16977894.lpF5TMN6fg--