infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-3628) Import SourceForge respositories to apache for incubator project Jena
Date Mon, 16 May 2011 14:39:47 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034035#comment-13034035
] 

Tony Stevenson commented on INFRA-3628:
---------------------------------------

Note, 

The checksum files seem to match. 

However, I nave also noted that data volume is quite large. 

-rw-r--r--  1 pctony  pctony   1.7G May 16 14:16 ASF-Jena-CVS.svn
-rw-r--r--  1 pctony  pctony   3.5G May 16 14:18 ASF-Jena-SVN.svn
-rw-r--r--  1 pctony  pctony   223M May 16 14:18 ASF-Joseki-CVS.svn

Essentially 5.5Gb.   

ASF-Jena-CVS == 9456 revs
ASF-Jena-SVN == 8842 revs
ASF-Joseki-CVS == 1102 revisions

Andy, I will have to schedule downtime to do the live import for this, due to the size of
the dataset.  However I will be running a test import, to measure time it takes to do each
of them. 


> Import SourceForge respositories to apache for incubator project Jena
> ---------------------------------------------------------------------
>
>                 Key: INFRA-3628
>                 URL: https://issues.apache.org/jira/browse/INFRA-3628
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Andy Seaborne
>            Assignee: Tony Stevenson
>
> Jena is project in incubation with an existing codebase, currently on SourceForge in
3 different repositories, SVN and CVS (2 SF projects).  We have software grants on file at
Apache for the majority of this code (in fact, for almost all of it).  We'd appreciate the
help migrating it to Apache infrastructure.
> We have several repositories, we'd like to import as-is, ideally with history, to create
a record of the software pre-Apache.
> Our SourceForge repositories are:
> CVS: jena.cvs.sourceforge.net:/cvsroot/jena
> CVS: joseki.cvs.sourceforge.net:/cvsroot/joseki
> SVN: https://jena.svn.sourceforge.net/svnroot/jena
> Our initial thoughts were to place each repository in its own area under a common root
to denote the imported code:
> https://svn.apache.org/repos/asf/incubator/jena/import/...
>   so
> https://svn.apache.org/repos/asf/incubator/jena/import/jena-cvs
> https://svn.apache.org/repos/asf/incubator/jena/import/jena-svn
> https://svn.apache.org/repos/asf/incubator/jena/import/joseki-cvs
> There are modules with the same name in the CVS and SVN repositories: some modules moved
from CVS to SVN with the same name - we don't need to integrate them as part of the move.
> In case it helps, the rsync backups are:
>  jena.cvs.sourceforge.net::cvsroot/jena/*
>  jena.svn.sourceforge.net::svn/jena/*
>  joseki.cvs.sourceforge.net::cvsroot/joseki/*
> They are: 1.2G, 2.3G and 409M respectively.
> After the import, we will be extracting the active modules and building a new project
structure, leaving the "import" area as the permanent record of out starting point at Apache.
 The import/ area becomes effectively a read-only archive.
> If this is not a sensible way for doing the imports, or there is better practice, or
we're just being plain daft, please let us know.  
>     Andy
>     jena-dev@incubator.apache.org

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message