You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ctakes.apache.org by "Johnsd11 (via GitHub)" <gi...@apache.org> on 2025/04/01 14:49:00 UTC
[I] [Question]: (CTAKES-10) Pre-Migration- Pre initial code base [ctakes]
Johnsd11 opened a new issue, #36:
URL: https://github.com/apache/ctakes/issues/36
### What’s your question?
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
### Context
_No response_
### What category does this question fall under?
None
### Contact Details
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@ctakes.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question]: (CTAKES-10) Pre-Migration- Pre initial code base [ctakes]
Posted by "Johnsd11 (via GitHub)" <gi...@apache.org>.
Johnsd11 commented on issue #36:
URL: https://github.com/apache/ctakes/issues/36#issuecomment-2769636311
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...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@ctakes.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question]: (CTAKES-10) Pre-Migration- Pre initial code base [ctakes]
Posted by "Johnsd11 (via GitHub)" <gi...@apache.org>.
Johnsd11 closed issue #36: [Question]: (CTAKES-10) Pre-Migration- Pre initial code base
URL: https://github.com/apache/ctakes/issues/36
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@ctakes.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question]: (CTAKES-10) Pre-Migration- Pre initial code base [ctakes]
Posted by "Johnsd11 (via GitHub)" <gi...@apache.org>.
Johnsd11 commented on issue #36:
URL: https://github.com/apache/ctakes/issues/36#issuecomment-2769635597
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@ctakes.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org