infra-issues mailing list archives

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


Tony Stevenson commented on INFRA-3628:

Sure.  I'll import them into the folders you created.  I'll let you know once it is done.
 It is likely to be tomorrow AM (BST).

> Import SourceForge respositories to apache for incubator project Jena
> ---------------------------------------------------------------------
>                 Key: INFRA-3628
>                 URL:
>             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:
> CVS:
> SVN:
> Our initial thoughts were to place each repository in its own area under a common root
to denote the imported code:
>   so
> 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:
> 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

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message