Plans for SVN infrastructure shutdown
luigi.toscano at tiscali.it
Sun Jan 20 23:12:32 GMT 2013
Ben Cooksley wrote:
> On Mon, Jan 21, 2013 at 9:09 AM, Luigi Toscano <luigi.toscano at tiscali.it> wrote:
>> But it's not the same situation.
>> For what I remember, even if I was not an active contributor at that time, the
>> new svn repository basically matched the content of the old one; moreover, the
>> structure was a bit different at that time. This is not the case with git,
>> where for example we would lose the content of unmaintaned (which is somehow
>> hidden). What if someone would like to continue a project from there?
> They will need to migrate the old project to Git first, before being
> able to make new commits to it.
Thank you, this is perfectly acceptable.
> It is not necessary to keep WebSVN alive to still allow the repository
> content to be accessed.
>> Also, even if non migrated projects in extragear and playground will be kept,
>> the lost of history does not sound good (same reasons as before, also because
>> it would make it impossible to solve problems related, for example, with
>> licensing or relicensing, should they arise).
> No loss of history will occur, the full Subversion repository will
> remain accessible via svn://.
> In case it was not already clear - svn:// access will be the only part
> of Subversion which will be retained.
> (Translation infrastructure is not affected by the above).
Thank you; this means can you please update the migration document, removing
the line "Close down of svn.kde.org. All extragear / playground projects still
in svn will be 'archived' with loss of history.", as it seems to not be the case?
More information about the kde-core-devel