incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen, Pei" <>
Subject RE: cTAKES 3.0 developer guide review
Date Tue, 12 Feb 2013 21:23:35 GMT
For developers looking to contribute code back to cTAKES, I would recommend trunk as the place
to begin...
A branch was created from trunk so that releases could be created but new development could
continue on with trunk (since we realized it may take some time to get this first release
out the door.).
A tag was created (always automatically by the mvn release plugin each time we create a rc)
to guarantee that we could always recreate a release from source.  [yes we can clone or rename
the -rc7 tag once it's has been successfully voted on and released]
There should be a very specific reason why someone would build from source and work directly
off a branch or a tag such as creating a release by a release manager or making a bug fix
to a branch for a patch release.

From: Bleeker, Troy C. []
Sent: Tuesday, February 12, 2013 2:39 PM
To: ''
Subject: RE: cTAKES 3.0 developer guide review

I thought that this might be the URL that would exist once 3.0 makes it through a release
candidate vote and becomes the first Apache cTAKES release. Is that incorrect?

But you're right it is a tag. I'm not a cTAKES code developer so my understanding may need
to be shaped here for the doc's sake. Developers will need to make changes to the current
tag and also make sure that those changes make it to the trunk (in almost every case). The
trunk may be unstable at any given time, but a tag should be relatively stable? Which one
would we suggest that a developer checkout if it is their first foray into cTAKES?

Perhaps a definition of how cTAKES uses tags and branches is in order. Here's my guess based
on what is there:
Branches - cTAKES uses SVN branches to delineate 1) major versions and 2) one-off attempts
at major functions. One-off attempts may or may not be merged back into the trunk in the future.
Tags - cTAKES uses SVN tags to delineate release candidates, betas, major releases and any
other stable points in time.

What's not in that definition is how we do fixes for a release. Let's say 3.0 is released.
Now we want a 3.0.1 for a critical item. Is that a tag or a branch?

-----Original Message-----
From: []
On Behalf Of Halgrim, Scott
Sent: Monday, February 11, 2013 11:55 AM
To: ''
Subject: RE: cTAKES 3.0 developer guide review

Thanks for putting this together, Troy.

Fwiw, the checkout URL on the guide (
doesn't exist. Not sure if it's meant to at some point or not.

Do we want devs checking out from tags instead of from trunk?


-----Original Message-----
From: Bleeker, Troy C. []
Sent: Friday, January 18, 2013 2:48 PM
To: ''
Subject: cTAKES 3.0 developer guide review

The developer guide is pretty close to complete then. If anyone could take the time to review
it, make changes. There are both expert install instructions and step by step.

I used what we think will be the URL for check out based on what James said.

Fill me in on how to select which run configuration and I can add it - or the beauty of the
wiki - you can too.

I assume someone will take care of deleting the empty directories at some point.

For the launch files I think there should only be 2 as well. Are these names better than what's
there now, more descriptive in the short space?


-----Original Message-----
From: []
On Behalf Of Masanz, James J.
Sent: Friday, January 18, 2013 12:08 PM
To: ''
Subject: RE: cTAKES 3.0 questions

There is a branch for 3.0

For each release candidate there is a tag such as

I'm assuming we will create a tag for the release without 'rcX' on the end once the release
is approved.

I don't think we need to document all the run configurations. I think we should just document
how to select which one of the twin to select Within the Run Configurations popup, look at
the Shared file field on the Common tab.

Yes, all the institutional directories are supposed to be gone. Looks like we missed an empty

James Masanz

> -----Original Message-----
> From:
> [
> org]
> On Behalf Of Bleeker, Troy C.
> Sent: Friday, January 18, 2013 11:29 AM
> To:
> Subject: cTAKES 3.0 questions
> Working through the dev install instructions I've come up with a
> number of questions. Could the group help me out ...
> Where will the non-volatile cTAKES 3.0 trunk be? Seems like the code
> here keeps changing:
> Once released will the code freeze at a particular place and will it
> have
> 3.0 in the URL in order to distinguish this release from an inevitable
> future release?
> Why are there 4 .launch files under ctakes-clicnical-
> pipeline/resources/launch? What's the difference?
> CPE cTAKES.launch
> CVD cTAKES.launch
> UIMA_CPE_GUI--clinical_documents_pipeline.launch
> UIMA_CVD--clinical_documents_pipeline.launch
> There are lots of Run Configurations now. Do we need a place to
> document all of those? All of them in my checkout on 1/14 appear to have a twin.
> Ctakes/ctakes-ne-contexts/target/classes/edu/mayo/bmi is created in my
> Eclipse projects upon checkout. Are not all the institutional
> directories supposed to be gone?
> Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics
> and Informatics
> Phone: 507-293-1574 * Fax: 507-284-0360 * Mayo
> Clinic * 200 First Street SW * Rochester, MN 55905 *


GHC Confidentiality Statement

This message and any attached files might contain confidential information protected by federal
and state law. The information is intended only for the use of the individual(s) or entities
originally named as addressees. The improper disclosure of such information may be subject
to civil or criminal penalties. If this message reached you in error, please contact the sender
and destroy this message. Disclosing, copying, forwarding, or distributing the information
by unauthorized individuals or entities is strictly prohibited by law.

View raw message