[Kde-scm-interest] Kopete git migration

[Urs Wolfer]

Okay, let's try to take the time frame between June 5th and June 11th.


* I will request the Git Repos until June 4th. @Pali: will you care for 
the Kopete repos; I will do all the others? See [1]. Please add also 
Jeremy and me as admins for these repos.

* @Jeremy: When will you have time to do the migration of all repos 
except Kopete?
* @Pali: When will you have time to do the migration of Kopete?

* I will notify the release team until June 4th if we agree on this 
plan.

* We need to look down SVN before we start with the migration. (who 
can/will do this?)

* After the migration, I will cherry-pick all the build / doc fixes from 
master into the 4.10 branch of every repo.

* After the migration, I will update the documentation paths file 
(l10n-kde4/scripts/documentation_paths for master and branch).

* After the migration, I will update the localization config 
(l10n-kde4/scripts/get_paths)

What's missing? Please help to complete this list.

Bye
urs


[1] 
http://community.kde.org/Sysadmin/GitKdeOrgManual#Requesting_project_migrations_from_KDE_SVN_or_Gitorious.org


On 2013-05-31 21:52, Jeremy Whiting wrote:
> On Fri, May 31, 2013 at 10:43 AM, Albert Astals Cid <aacid at kde.org>
> wrote:
> 
>> El Divendres, 31 de maig de 2013, a les 17:37:22, Urs Wolfer va
>> escriure:
>> 
>>> Ok, let's check what's the current status:
>>> 
>>> filesharing, krdc, and now also kdenetwork-strigi-analyzers are
>>> maintainer approved.
>>> 
>>> kdnssd and kppp have been shorty checked by me and they look ok
>> (though
>>> it would be a good idea if somebody else could check also).
>>> 
>>> kopete: @Pali, is it ready?
>>> 
>>> the krfb maintainer has not answered yet; probably we should
>> check that
>>> repo as well.
>>> 
>>> @Jeremy: Anything that needs to be done before the final
>> conversion?
>> 
>> Coordinate with the release team so you don't do the move close to
>> any release
>> date and with the i18n team so we update the scripty files.
> 
> Yep, looking at the kde calendar, 4.10.4 is to be released next
> tuesday (June 4th) and then 4.11 beta 1 will be tagged on June 12th,
> so we ought to try to shoot for that window, preferably as early as
> possible in that window so any issues can get fixed before 4.11 beta 1
> tagging.
> 
> Urs, did you file the bugs for the git repos yet? or shall I do that?