[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Plans for SVN infrastructure shutdown
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2013-01-20 22:53:04
Message-ID: CA+XidOHRNQt23=i4qoetft_=EtrQah7MJpq9+hN6bmxUCG6i5g () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jan 21, 2013 at 9:09 AM, Luigi Toscano <luigi.toscano@tiscali.it> w=
rote:
> Ben Cooksley wrote:
>> On Sat, Jan 5, 2013 at 10:45 AM, Oswald Buddenhagen <ossi@kde.org> wrote=
:
>>> On Wed, Jan 02, 2013 at 06:52:32PM -0300, Nicol=E1s Alvarez wrote:
>>>> http://community.kde.org/Sysadmin/SVNInfrastructureShutdown
>>
>> Hi Oswald,
>>
>>>>
>>> this whole thing ignores that svn is still simply the better option for
>>> certain types of content - multimedia data in particular.
>>
>> Correct. We'll keep an eye on Git's progress in this area to see if
>> anything workable comes up.
>> If nothing does, we will adjust our plans as needed at the appropriate
>> stage of the plan.
>
> Does the rollback plan include also troubles or problems or bad feedback =
from
> translators? The plan only says:

The plan has been fully discussed with the translations co-ordinator,
Albert Astals Cid.

>
> "The only exception are the translations. These will continue to happen v=
ia
> subversion, but this will use the gitolite software as backend, in any ca=
se,
> this will result in only minor changes for translators."
>
> Can you please elaborate more about those changes? I haven't seen no
> discussion on the relevant mailing list. I miss last Akademy as well, so =
maybe
> it was discussed there, but it would be better to know what's going on be=
fore
> it's too late

The change will consist of a single, one-time execution of "svn switch
--relocate" which translators will need to perform if they make
commits.
This was not discussed at Akademy, but on IRC in #kde-sysadmin.

>
>
>>
>>> of course git could be hacked to Not Suck for such content (fully
>>> functional shallow and narrow clones, lazy fetching, etc.), but to my
>>> knowledge this has not happend yet (i make no claim to being fully
>>> up-to-date).
>>
>> Regards,
>> Ben
>>
>

Regards,
Ben Cooksley
KDE Sysadmin
[prev in list] [next in list] [prev in thread] [next in thread]