[Kde-scm-interest] Kopete git migration

[Urs Wolfer]

Ok, all repos (except Kopete) are now ready on projects.kde.org.

See sysadmin response:
---------------------------

The repository and projects.kde.org entries have been set up, with the 
admin and description as you indicated.

Scripty will be adjusted automatically to retrieve the sources from the 
new locations once the initial push has been completed and the project 
admins have filled in the trunk and stable i18n branch information in 
Settings -> Repository for each project. Note that if you do not have a 
stable branch you should set none in the stable i18n branch and not 
master.

LXR and EBN will be adjusted automatically at their next run, which 
might take max a week.

The ReviewBoard entry will be set up by David after you have pushed and 
reopened this ticket.

Please note that you will need to run the "hooks enable" server-side 
command after the initial push to enable the email hooks and write 
access to non-repo-admins: 
http://community.kde.org/Sysadmin/GitKdeOrgManual#hooks-enable

You should also remove the sources from SVN after completing the push so 
scripty doesn't get confused by sources being found in two places at 
once. The customary way to do this is to initially replace the folder 
contents with a README file pointing at the new location, and then to 
remove the entire folder a few weeks later.

Also please note that git push --all does not push tags. git push --tags 
does.
This is frequently forgotten. Both arguments cannot be used at the same 
time.

Please reopen this bug after the push has been completed.  IMPORTANT: 
please ensure the repository setting Enable development sites is enabled 
on KDE Projects in Settings -> Repository. Else no translations can be 
made.

---------------------------

@Jeremy: when will you be ready to do the final migration? I think it 
would be best if you also could remove the source from SVN and add a 
readme file like suggested above.

@Pali: now you can also request the repos. I think it would be best when 
you do the conversion at the same time as Jeremy will do it.

Bye
urs

On 2013-06-01 13:27, Albert Astals Cid wrote:
> El Dissabte, 1 de juny de 2013, a les 12:15:37, Pali Rohár va escriure:
>> On Saturday 01 June 2013 11:53:48 Urs Wolfer wrote:
>> > 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.
>> 
>> Ok. There is main kdenetwork kopete repository and these
>> playground/extragear plugin repositories:
>> 
>> kopete-pimpresence
>> kopete-scripting
>> kopete-sharemydesktop
>> kopete-thinklight
>> kopete-whiteboard
>> 
>> > * @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?
>> 
>> What is needed? Only "generate" git repositories from svn? I can
>> start conversion & filter script on dewey, just write me mail.
>> 
>> > * 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.
>> 
>> * update links for krazy source code checker on EBN
>> * update links for documentation generator on api.kde.org
>> * migrate/create projects on git reviewboard
> 
> reviewboard is done by sysadmins when you ask for the git repo.
> 
> Cheers,
>   Albert
> 
>> 
>> > Bye
>> > urs
>> >
>> >
>> > [1]
>> > http://community.kde.org/Sysadmin/GitKdeOrgManual#Requesting_p
>> > roject_migrations_from_KDE_SVN_or_Gitorious.org
>> 
>> What will happen with patches on svn reviewboard?
> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest at kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest