[
https://issues.apache.org/jira/browse/CTAKES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421807#comment-13421807
]
Pei Chen commented on CTAKES-10:
--------------------------------
1) branches/trunk/tags directories have been created in Apache cTAKES's SVN
repo (Done)
2) The latest branch from SF (SHARPn-cTAKES) which was slated for the 2.6
release has been added to branches (Done)
3) TODO: Build and create a 2.6 release with the existing codebase/structure?
Any volunteers...?
4) Also added the maven-sandbox branch which we can reuse the pom's. (Done)
5) svndump of current entire ohnlp repo (In progress- seems to be >6GB). Any
suggestions where to persist this dump file? Somewhere on ASF's SVN?
6) I would suggest we can use the SHARPn-cTAKES branch and maven-sandbox to
begin working on what the new Apache cTAKES code/package will look like in
/trunk..
7) All of known developers from SF have already been invited to join this
group...
> Pre-Migration- Pre initial code base from sourceforge to ASF SVN
> ----------------------------------------------------------------
>
> Key: CTAKES-10
> URL: https://issues.apache.org/jira/browse/CTAKES-10
> Project: cTAKES
> Issue Type: Task
> Reporter: Pei Chen
> Assignee: Pei Chen
> Original Estimate: 1,344h
> Remaining Estimate: 1,344h
>
> Agree on how do we migrate from sourceforge SVN to Apache SVN (One option is
> to create an exact copy of current SVN from sourceforge and check it into
> Apache in order to have a complete audit trail of refactoring changes made
> within Apache.)
> I think that this is a good idea, but I think that we might
> do well committing refactoring changes to a branch and then when –done- (we
> need to have defined goals) move the branch to trunk all in a single go.
> That way the trunk history has a decent starting point. But I don’t think
> that it really much matters. SPF
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
