incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: SVN source structure for Apache cTAKES?
Date Mon, 23 Jul 2012 19:54:43 GMT
Hi Steve,

On Jul 23, 2012, at 10:31 AM, Steven Bethard wrote:
>> [..snip..]
>> 
>> Besides that though, isn't changing the package names something that could be easily
scripted? We did
>> so for Apache OODT within a matter of a few days during Incubation with some Perl
and Python scripting.
> 
> Changing them is not trivial because of UIMA's use of XML descriptors, which makes tracking
down all the places where you might need to change a package some extra work. I agree it could
be scripted, but the additional work is in getting all the tests running again and other quality
control measures that are necessary before a release.

Sure, it's extra work, but I think worth it and not too cumbersome (like writing new code
;) ).

> 
> Another reason not to change the package names before the 2.6 release is that there are
other package name changes that probably should be made, and it would be best to make all
package name changes at the same time we change to org.apache.ctakes. (Otherwise we have a
more painful upgrading process for the users.)

I would encourage you guys to simply release early, and release often, even if you have to
issue
bugfixes, or updates, etc., getting releases out there for feedback is preferred to waiting
until 
hypothetical situations come true, or for design decisions to be solidified. Release numbering
and naming can help here.

> 
> But since the package name is not required, maybe a way forward would be to:
> 
> (1) Just get cTAKES, as is, into the Apache repository, and make the 2.6 release exactly
as planned (no code changes at all) from the Apache repository.
> 
> (2) Immediately after the 2.6 release, change the package names to org.apache.ctakes,
and use that for the 2.7 and subsequent releases.

This is a good option to consider. Thanks for being proactive in proposing it Steve.

Cheers,
Chris

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


Mime
View raw message