Support #35574

Transfer EXT:caretaker to GIT

Added by Thomas Hempel about 1 year ago. Updated about 1 year ago.

Status:Closed Start date:2012-04-03
Priority:Should have Due date:
Assignee:Karsten Dambekalns % Done:

100%
Category:Migration
Target version:-
Votes: 2 (View)

Description

Hi,

as discussed with Karsten, we'd like to have EXT:caretaker as GIT repository rather than SVN. We'd also like to split up the repository.

Can you please duplicate the repository into

caretaker
caretaker_addons

Thank you very much and best wishes,
The caretaker team

Related issues

related to git.typo3.org - Bug #36048: create a git repo instead of svn for new registered project New 2011-09-28 2012-07-05

History

#1
Updated by Thomas Hempel about 1 year ago

ping Any news on this?

#2
Updated by Michael Stucki about 1 year ago

I am not sure if Karsten will take care of this. Actually I would rather like to see our energy spent on a generic solution since more and more requests for Git repository conversions will come up. Who can take care of this?

#3
Updated by Michael Stucki about 1 year ago

Ah, Steffen already made a nice statement in #36048:

There is no way to create repositories automatically at the moment. Therefore there is no Git support for community extensions, yet.

Peter Niederlag is working hard on this and sometimes creates repos to improve the creation process step by step.

But please don't create hundreds of issues to migrate your project

We will announce, once there is this possibility for everyone.

#4
Updated by Michael Stucki about 1 year ago

  • Assignee deleted (Karsten Dambekalns)

#5
Updated by Thomas Hempel about 1 year ago

  • Assignee set to Karsten Dambekalns

I spoke to Karsten in person in Munich during the F3X and he volunteered to do this change. It was actually his idea to create this ticket. ;-)

I totally understand, that you don't want countless of this issues in the tracker but please keep this assigned to him. I'll send him a reminder. If he can't do it we will simply move the rep to our own server and I remove this ticket. Promised!

Best wishes,
Thomas

#6
Updated by Karsten Dambekalns about 1 year ago

The script we used to migrate existing repositories has not yet been updated to work with the new way gerrit stores internal data. Since AFAIK Peter is working on this, I'd not do this on my own now…

#7
Updated by Thomas Hempel about 1 year ago

  • % Done changed from 0 to 100

Alright then. We will switch somewhere else for the time being.

Thanks and Greets,
Thomas

P.S.: This can be closed now. ;-)

#8
Updated by Karsten Dambekalns about 1 year ago

  • Status changed from New to Closed

Sorry for the hassle!

#9
Updated by Peter Niederlag about 1 year ago

There is no way we can support to automate splitting of reps. Also one rep requires one forge project. Probably no way we can support multiple reps per project in the near future. A simple svn2git migration is something we hope to support pretty soon though...

#10
Updated by Karsten Dambekalns about 1 year ago

Peter Niederlag wrote:

Also one rep requires one forge project. Probably no way we can support multiple reps per project in the near future.

Well, it would be hard to actually link (e.g. show them in the repository tab) them from the forge project. But the other way round - use one forge project to define group membership of mutiple gerrit projects - is no problem.

Anyway, subprojects under an umbrella are probably the best option in Forge.

Also available in: Atom PDF