Posted by sdboyer on April 25, 2010 at 6:35pm
8 followers
Jump to:
| Project: | The Great Git Migration |
| Component: | Migration scripts |
| Category: | task |
| Priority: | critical |
| Assigned: | neclimdul |
| Status: | postponed |
| Issue tags: | git low hanging fruit, git phase 2, git sprint 10, tggm db-repo mirroring |
Issue Summary
Since git repo creation will occur strictly by trigger, anything in contributions/{modules,themes} that doesn't have a corresponding project already is going to be orphaned. So we need to decide prior to pulling the trigger how we'll handle those projects.
Comments
#1
Forgot to mention translations.
#2
Tagging. This might be a good task for a volunteer to do.
#3
Create an 'unofficial project' page for them with just a title?
#4
So mainly when I wonder how to solve a problem like this I'd actually try to think of how a typical repository browser would handle it. I assume this is different; that we are talking about creating an actual project node for each project automatically? Does the repository browser then link to this? If one is not created could that potentially just be a link to create a project page manually?
#5
I vote to ignore them. If there's no project node, it's not relevant. The history will still be in CVS if someone wants to get it. I'm assuming we're going to need to have a way to do targeted imports after the One Big Conversion(tm), anyway, so if someone really wants to, they can file an infra issue requesting that their orphaned code gets Git-ified. I'd vastly prefer ignore and handle special cases later (if at all) than bulk creating project nodes for things that are basically abandoned code to begin with.
#6
I tend to agree, too. As does webchick. To keep the migration scripts clean, that'll probably mean adding a step in that hudson job which blows away projects after the whole build has taken place if they don't have corresponding entries in the db.
So, since we're decided on that, retitling & marking critical so that this issue can be the place we track actually DOING this.
#7
Tagging for Git Sprint 9
#8
one of the mirroring issues
#9
Neclimdul told me I could assign this to him.
#10
This is something I should be able to take a look at.
#11
Postponed till I get to all the mirroring issues next week.
#12
D6 branch has 1 minor bug #1176524: Remove CVS $Id$ tags from core