[
https://issues.apache.org/jira/browse/CTAKES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415605#comment-13415605
]
Pei Chen commented on CTAKES-10:
--------------------------------
Starting the discussion on how should the new SVN structure look like for
Apache cTAKES.
Currently in SF, it looks like:
{cTAKES-root}
/branches
/tags
/trunk
-/cTAKES
-/core
/src
/desc
-/chunker
-/coref-resolver
Etc..
Which means that all of those projects are all children of trunk and will share
the same release cycle.
One alternative option looks something like (each component could have it’s own
trunk/jar file?):
{cTAKES-root}
-/ctakes-core
/trunk
/src
/java
/main
/resources
/branches
/tags
-/ctakes-chunker
/trunk
/src
/java
/main
/resources
/branches
/tags
-/ctakes-coreference
/trunk
/src
/java
/main
/resources
/branches
/tags
There are pro’s and con’s to both, but let’s get the discussion started as this
will be required for the code migration.
> 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: Joern Kottmann
> 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
