infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15016) New Subversion repository opennlp-corpus
Date Wed, 27 Sep 2017 21:34:00 GMT

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

Greg Stein commented on INFRA-15016:
------------------------------------

Alrighty. We've talking about how to manage this. Our working plan is:

* create a new svn repository at svn.apache.org/repos/bigdata/
* set up a bigdata/opennlp/ directory, with appropriate permissions
* work with you to get that initial import done (restarting 25 Gb commits is a pain)
* we will monitor the new repository, possibly applying a bit of rate-limiting if we see problems
* this future proofs us, if we need to move this svn repository to a new machine/datacenter
to deal with bandwidth/capacity issues

Would this new svn repository approach work for your project?

I think that we're going to want to move the files-to-commit onto ASF hardware before performing
the commit. We'll need to devise a plan to get the files moved from $wherever onto an ASF
box.


> New Subversion repository opennlp-corpus
> ----------------------------------------
>
>                 Key: INFRA-15016
>                 URL: https://issues.apache.org/jira/browse/INFRA-15016
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Subversion
>            Reporter: Joern Kottmann
>            Assignee: Greg Stein
>
> We would like to get a new subversion repository to store large text files.
> Our understanding from previous talks with Infra about this is that our preferred option,
git, is not suitable for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message