Return-Path: X-Original-To: apmail-incubator-opennlp-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-opennlp-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F3645982A for ; Wed, 15 Feb 2012 09:13:32 +0000 (UTC) Received: (qmail 1486 invoked by uid 500); 15 Feb 2012 09:13:32 -0000 Delivered-To: apmail-incubator-opennlp-dev-archive@incubator.apache.org Received: (qmail 1374 invoked by uid 500); 15 Feb 2012 09:13:32 -0000 Mailing-List: contact opennlp-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: opennlp-dev@incubator.apache.org Delivered-To: mailing list opennlp-dev@incubator.apache.org Received: (qmail 1363 invoked by uid 99); 15 Feb 2012 09:13:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 09:13:32 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.171] (HELO moutng.kundenserver.de) (212.227.126.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 09:13:22 +0000 Received: from [132.230.176.24] (cl8.averbis.uni-freiburg.de [132.230.176.24]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MJF9e-1RuqpT3rkg-003AD1; Wed, 15 Feb 2012 10:13:02 +0100 Message-ID: <4F3B7723.5040107@averbis.com> Date: Wed, 15 Feb 2012 10:13:07 +0100 From: Katrin Tomanek User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: opennlp-dev@incubator.apache.org Subject: Intermediate Release Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:DFiETXheDLHq7HZtwfYkg8p8SPm8ZXyaP5KWThUME9i gQ/GllemLk44WMKy0bPMaWxm2Z4KitLEoUIBbfk3LHMtQ8cxrj MUT9uXeqYuQuhh3ieb0dIY298aNBpnMdUJ48IJIAlx3ZB3BDLQ KNyI91T2kDs0R/nUtOX3hEiHj6za2o2GNP2a5lbd4cMRTupl1q CPouMs69sZHCNBj3JSxa2R3zimVDEszI0vyJ24xutfpihL2zqh qNi0/h8Nl7QFQu8hGLXAtQZva5SVr3rg9jOISeKjMBiTRBv/gq zTNHimRiMgvGNzGLcsF4PCWXdHXKzYSnir8o3fthXcED7U0rLN FfW4qpVCx3zeYTV43G2uiWGTassrl+jk6/eOI+APS X-Virus-Checked: Checked by ClamAV on apache.org Hi, I've been asking before about the plans for the next opennlp release. The answer I got was that it's not planned yet, when (and whether) to release 1.5.3 (maybe, there will be a 1.6. as the next release). My situation now is the following: I need a release by the end of next month (since we are using opennlp in a commercial product where we are having a deadline). I cannot use 1.5.2 (because of the EOS symbol problems that are fixed in the trunk). So, I am planning to build a transitional release in our company-internal repository. I am just wondering what would be the best time to do so.... I see that currently, there are still issues on the POS Tagger factory. About other problems I am currently not aware... Any hints about when to build such a transitional release which I could consider "kind-of" stable? Thanks, Katrin P.S.: let me know if there are currently any issues I could be working on...