You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2013/04/29 19:56:15 UTC
[jira] [Comment Edited] (INFRA-5936) Migrate Apache Cayenne to Git
[ https://issues.apache.org/jira/browse/INFRA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644686#comment-13644686 ]
Andrus Adamchik edited comment on INFRA-5936 at 4/29/13 5:56 PM:
-----------------------------------------------------------------
David, we had a conversation on dev list about the migration, and maybe we can simplify your task (and the life of future users who will try to git-clone Cayenne) by trimming the depth and the breadth of the migrated "cayenne/main" tree. FWIW, my own git-svn local copy that starts with SVN rev 450260 from 2006 is "only" 364M in size :)
So anyways, we only care about the code that belongs to 3.0 release and newer, as this is when a Maven migration has occurred and various dependency jars were removed from the repo. We'll keep SVN around as an archive of the prior history. What that means is that we need to only preserve branches STABLE-3.0, STABLE-3.1, and matching release tags 3.0* and 3.1*. As for the earliest revision we can arbitrarily pick r498273 that happened on Jan 21, 2007 when we graduated from the Incubator and started moving code to its present location.
This should preserve just enough "modern" history that we care about and should hopefully speed up the migration and produce a manageable repo.
was (Author: andrus):
David, we had a conversation on dev list about the migration, and maybe we can simplify your task (and the life of future users who will try to git-clone Cayenne) by trimming the depth and the breadth of the migrated "cayenne/main" tree. FWIW, my own git-svn local copy that starts with SVN rev 450260 from 2006 is "only" 364M in size :)
So anyways, we only care about the code that belongs to 3.0 release and newer, as this is when a Maven migration has occurred and various dependency jars were removed from the repo. We'll keep SVN around as an archive of the prior history. What that means is that we need to preserve branches STABLE-3.0, STABLE-3.1, and matching release tags 3.0* and 3.1*. For the earliest revision we can arbitrarily pick r498273 that happened on Jan 21 when we graduated from the Incubator and started moving code to its present location.
This should preserve just enough "modern" history that we care about and should hopefully speed up the migration and produce a manageable repo.
> Migrate Apache Cayenne to Git
> -----------------------------
>
> Key: INFRA-5936
> URL: https://issues.apache.org/jira/browse/INFRA-5936
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Andrus Adamchik
> Assignee: David Nalley
>
> Apache Cayenne would like to migrate our SVN repo to Git [1]. We would like to split various independent folders of our SVN [2] into independent Git repos. Let's start with the core module [3]. If I understand correctly once Git setup for Cayenne is done, we will be able to create new repos on our own without bothering infra? If that's the case, we'll be happy to do all migration ourselves as soon as we are given access and some guidance as to the ASF Git setup.
> Our main Infra contacts for Git migration are 'aadamchik' (myself) and 'amaniatis'.
> Thanks,
> Andrus
> [1] http://markmail.org/message/4grvfh5yxlmgqzm3
> [2] http://svn.apache.org/repos/asf/cayenne/
> [3] http://svn.apache.org/repos/asf/cayenne/main/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira