Hi Chris,
Steve and el. is correct.  There was a previously pending release currently in 
SourceForge (called 2.6) scheduled some time ago.
Our plan is to make a clean break from SourceForge after this release to avoid 
any duplicate effort as you suggested.  And going forward we anticipate that 
all work should be done from the Apache SVN.
We didn't document the actual plan yet on the proposal as to how the actual 
migration would occur thinking that it would be part of the incubation process.
Hope it clarifies things.

Thanks again.
--Pei


-----Original Message-----
From: Mattmann, Chris A (388J) [mailto:[email protected]] 
Sent: Friday, July 20, 2012 2:48 PM
To: <[email protected]>
Subject: Re: SVN source structure for Apache cTAKES?

Hi Pei,

On Jul 20, 2012, at 10:59 AM, Chen, Pei wrote:

> Sounds good. We'll start this over the next several weeks (after the current 
> cTAKES 2.6 release).

Can you shed some light here? 

What current release are you talking about? I would encourage you not to 
duplicate development especially while you now have a project at the ASF 
incubator called Apache cTakes (incubating). Moreover, releasing software at 
the external, pre-Apache community can potentially cause confusion (and 
maintenance woes) downstream especially for Apache cTAKES and can cause folks 
to just not come here or avoid coming here at all from a user and developer 
perspective.

I'd really as a mentor like to know more about what's going on here, so 
hopefully you (or someone else involved) can shed some light.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department University of Southern 
California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to