Hi Michael, The next release should also address the opennlp part of https://issues.apache.org/jira/browse/UIMA-475 Actually, the bug shows up with 2.2.1 but I cannot reproduce it on the current svn code. Since nobody has specifically fixed this bug it will require more investigation.
Eddie On Feb 4, 2008 10:47 AM, Michael Baessler <[EMAIL PROTECTED]> wrote: > Hi, > > we have two major items where projects are waiting for, so we should > consider to make the next bugfix release. The major items are: > - capabilityLanguageFlow performance fix > - FeaturePath implementation > > Probably there are some other open issues that should be fixed before > starting the next release. > When searching JIRA I see: > > UIMA-739 Use compressed form of eclipse update site, and support > multiple releases > UIMA-734 Check and possibly update docs for capability language flow > to say not to depend on subtyping > UIMA-733 it is possible to load a type system descriptor that > redefines the super type of the DocumentAnnotation > UIMA-727 Result Specifications not being passed to imbedded Pears > UIMA-704 adjustExamplePaths.bat creates broken .classpath for > uimaj-examples > UIMA-680 CAS is not unlocked on Errors > UIMA-657 Eclipse Update site should keep previous versions > UIMA-687 Remove redundant notifyAll when calling casPool.releaseCas > (...) > UIMA-643 TypeSystemUtil.type2TypeDescription() throws NPE when the > superType is null > UIMA-282 Work well with Apache logging (Log4J) > > I think most of them should be fixed before the next release. Other > opinions? > > Since the next release will also be a bug fix release I would suggest to > rename the version number from 2.3 to 2.2.2. > Would it be feasible to have the release in March? So we have some time > for fixing the open issues before we start the release cycle which will > take us about 5 weeks after code freeze. > > -- Michael > >
