You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Jörn Kottmann <ko...@gmail.com> on 2012/09/12 15:56:38 UTC
Next release
Hi all,
it has been a while since we released 1.5.2 and to me it looks
like its time for 1.5.3. I usually work now with the trunk version
because it just contain too many fixes I need for my day job.
I will volunteer to be release manager if nobody else wants to
take this role.
Any opinions?
Jörn
Re: Next release
Posted by Rodrigo Agerri <ro...@ehu.es>.
On Mon, Feb 18, 2013 at 2:56 PM, Jörn Kottmann <ko...@gmail.com> wrote:
> On 02/18/2013 02:27 PM, Rodrigo Agerri wrote:
>>
>> If it is of any help, I have been using the coreference module with
>> jwnl 1.4_rc3 and it works.
>
>
> Did you use the provided models, or did you train with your own data?
The provided models.
Cheers,
R
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/18/2013 02:27 PM, Rodrigo Agerri wrote:
> If it is of any help, I have been using the coreference module with
> jwnl 1.4_rc3 and it works.
Did you use the provided models, or did you train with your own data?
Thanks,
Jörn
Re: Next release
Posted by Rodrigo Agerri <ro...@ehu.es>.
Hello,
If it is of any help, I have been using the coreference module with
jwnl 1.4_rc3 and it works.
Cheers,
Rodrigo
On Mon, Feb 18, 2013 at 1:56 PM, William Colen <wi...@gmail.com> wrote:
> With jwnl 1.4_rc3 the code at least compiles.
>
> Also, it would be nice if someone familiar with the Coreference module
> could add some tests to the test plan:
>
> https://cwiki.apache.org/OPENNLP/testplan153.html
>
>
> On Sun, Feb 17, 2013 at 10:07 PM, Lance Norskog <go...@gmail.com> wrote:
>
>> OPENNLP-510 Maven dependency on jwnl is broken
>>
>> The version of JWNL used in coreference does not have an available Maven
>> download. This made it hard to add OpenNLP to the Lucene/Solr project.
>>
>> That project made a final (abandonment) release that is in Maven.
>> http://search.maven.org/#**artifactdetails%7Cnet.sf.**
>> jwordnet%7Cjwnl%7C1.4_rc3%**7Cjar<http://search.maven.org/#artifactdetails%7Cnet.sf.jwordnet%7Cjwnl%7C1.4_rc3%7Cjar>
>>
>> Are there any coref users out there? Could you please check if this
>> version works?
>>
>>
>> On 12/19/2012 12:17 PM, Jörn Kottmann wrote:
>>
>>> Lets start to get the release done, are there any issues expect the two
>>> open
>>> ones which need to go into this release ?
>>>
>>> Open issues are:
>>> OPENNLP-541 Improve ADChunkSampleStream
>>> OPENNLP-402 CLI tools and formats refactored
>>>
>>> Jörn
>>>
>>> On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
>>>
>>>> Hi all,
>>>>
>>>> it has been a while since we released 1.5.2 and to me it looks
>>>> like its time for 1.5.3. I usually work now with the trunk version
>>>> because it just contain too many fixes I need for my day job.
>>>>
>>>> I will volunteer to be release manager if nobody else wants to
>>>> take this role.
>>>>
>>>> Any opinions?
>>>>
>>>> Jörn
>>>>
>>>
>>>
>>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/18/2013 01:56 PM, William Colen wrote:
> With jwnl 1.4_rc3 the code at least compiles.
>
> Also, it would be nice if someone familiar with the Coreference module
> could add some tests to the test plan:
>
> https://cwiki.apache.org/OPENNLP/testplan153.html
The coref code uses wordnet ids directly in the feature generation,
in an update from a previous version to 1.3 these ids changed and
the models had to be re-trained.
We need to investigate if an update would change the ids again,
its probably easier and safer to get the repository problem solved for now,
and then for 1.6 we should find a better solution, e.g. moving the coref
stuff to the sandbox until we are able to train and test it.
Anyway this whole thing should not stop us from producing our first
RC so we can start testing.
+1 to place jwnl 1.3 in a stable repository before we release.
Jörn
Re: Next release
Posted by William Colen <wi...@gmail.com>.
With jwnl 1.4_rc3 the code at least compiles.
Also, it would be nice if someone familiar with the Coreference module
could add some tests to the test plan:
https://cwiki.apache.org/OPENNLP/testplan153.html
On Sun, Feb 17, 2013 at 10:07 PM, Lance Norskog <go...@gmail.com> wrote:
> OPENNLP-510 Maven dependency on jwnl is broken
>
> The version of JWNL used in coreference does not have an available Maven
> download. This made it hard to add OpenNLP to the Lucene/Solr project.
>
> That project made a final (abandonment) release that is in Maven.
> http://search.maven.org/#**artifactdetails%7Cnet.sf.**
> jwordnet%7Cjwnl%7C1.4_rc3%**7Cjar<http://search.maven.org/#artifactdetails%7Cnet.sf.jwordnet%7Cjwnl%7C1.4_rc3%7Cjar>
>
> Are there any coref users out there? Could you please check if this
> version works?
>
>
> On 12/19/2012 12:17 PM, Jörn Kottmann wrote:
>
>> Lets start to get the release done, are there any issues expect the two
>> open
>> ones which need to go into this release ?
>>
>> Open issues are:
>> OPENNLP-541 Improve ADChunkSampleStream
>> OPENNLP-402 CLI tools and formats refactored
>>
>> Jörn
>>
>> On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
>>
>>> Hi all,
>>>
>>> it has been a while since we released 1.5.2 and to me it looks
>>> like its time for 1.5.3. I usually work now with the trunk version
>>> because it just contain too many fixes I need for my day job.
>>>
>>> I will volunteer to be release manager if nobody else wants to
>>> take this role.
>>>
>>> Any opinions?
>>>
>>> Jörn
>>>
>>
>>
>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/19/2013 11:55 AM, Aliaksandr Autayeu wrote:
>> Lets start to get the release done, are there any issues expect the two
>>> >>open
>>> >>ones which need to go into this release ?
>>> >>
>>> >>Open issues are:
>>> >>OPENNLP-541 Improve ADChunkSampleStream
>>> >>OPENNLP-402 CLI tools and formats refactored
>>> >>
>> >Jörn, can you remind me what remains there? I've seen you commit on the
> simplification you proposed and although I didn't agree earlier, after I
> saw what you did - it does make sense.
On OPENNLP-402 I assumed lazy consensus, and fixed the two concerns I
stated on the issue,
anyway should something be changed, or is it fine how it is now?
The whole command line interface refactoring is a big step forward,
especially the possibility
to train directly on a corpus without converting it first manually.
Jörn
Re: Next release
Posted by Aliaksandr Autayeu <al...@autayeu.com>.
On 12/19/2012 12:17 PM, Jörn Kottmann wrote:
> Lets start to get the release done, are there any issues expect the two
>> open
>> ones which need to go into this release ?
>>
>> Open issues are:
>> OPENNLP-541 Improve ADChunkSampleStream
>> OPENNLP-402 CLI tools and formats refactored
>>
> Jörn, can you remind me what remains there? I've seen you commit on the
simplification you proposed and although I didn't agree earlier, after I
saw what you did - it does make sense.
Aliaksandr
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/19/2013 02:37 PM, William Colen wrote:
> Should we try to upload it to Central Repo using "jwnl" as groupid? What do
> you think?
+1, if that is possible it would be preferable for us, if they want to
use another group id we
can just update our pom to the new group id.
Jörn
Re: Next release
Posted by Benson Margulies <bi...@gmail.com>.
yes, ossrh will do that
On Feb 19, 2013, at 8:38 AM, William Colen <wi...@gmail.com> wrote:
> Should we try to upload it to Central Repo using "jwnl" as groupid? What do
> you think?
>
>
> On Mon, Feb 18, 2013 at 3:03 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> upload to central via ossrh.
>>
>> On Feb 18, 2013, at 12:46 PM, William Colen <wi...@gmail.com>
>> wrote:
>>
>>> We are using "jwnl" as groupid, I don't know if we can upload using this
>>> groupid. The best would be to reflect the Java package, which is
>>> net.didion.jwnl, or to follow the one used by 14. rc3, which
>>> is net.sf.jwordnet.jwnl.
>>> But changing the groupid would not help the already released OpenNLP
>>> versions.
>>>
>>>
>>> On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann <ko...@gmail.com>
>> wrote:
>>>
>>>> On 02/18/2013 03:17 PM, William Colen wrote:
>>>>
>>>>> I suppose we can't use opennlp.apache.org to host it, can we?
>>>> We probably could somehow distribute it from Apache servers, but if we
>>>> can get it into the central maven repository it would also fix the issue
>>>> for the already
>>>> released OpenNLP versions as far as I know.
>>>>
>>>> Here is a guide which explains the process:
>>>> https://docs.sonatype.org/**display/Repository/Uploading+**
>>>> 3rd-party+Artifacts+to+The+**Central+Repository<
>> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
>>>
>>>>
>>>> Jörn
>>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Should we try to upload it to Central Repo using "jwnl" as groupid? What do
you think?
On Mon, Feb 18, 2013 at 3:03 PM, Benson Margulies <bi...@gmail.com>wrote:
> upload to central via ossrh.
>
> On Feb 18, 2013, at 12:46 PM, William Colen <wi...@gmail.com>
> wrote:
>
> > We are using "jwnl" as groupid, I don't know if we can upload using this
> > groupid. The best would be to reflect the Java package, which is
> > net.didion.jwnl, or to follow the one used by 14. rc3, which
> > is net.sf.jwordnet.jwnl.
> > But changing the groupid would not help the already released OpenNLP
> > versions.
> >
> >
> > On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann <ko...@gmail.com>
> wrote:
> >
> >> On 02/18/2013 03:17 PM, William Colen wrote:
> >>
> >>> I suppose we can't use opennlp.apache.org to host it, can we?
> >> We probably could somehow distribute it from Apache servers, but if we
> >> can get it into the central maven repository it would also fix the issue
> >> for the already
> >> released OpenNLP versions as far as I know.
> >>
> >> Here is a guide which explains the process:
> >> https://docs.sonatype.org/**display/Repository/Uploading+**
> >> 3rd-party+Artifacts+to+The+**Central+Repository<
> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
> >
> >>
> >> Jörn
> >>
>
Re: Next release
Posted by Benson Margulies <bi...@gmail.com>.
upload to central via ossrh.
On Feb 18, 2013, at 12:46 PM, William Colen <wi...@gmail.com> wrote:
> We are using "jwnl" as groupid, I don't know if we can upload using this
> groupid. The best would be to reflect the Java package, which is
> net.didion.jwnl, or to follow the one used by 14. rc3, which
> is net.sf.jwordnet.jwnl.
> But changing the groupid would not help the already released OpenNLP
> versions.
>
>
> On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann <ko...@gmail.com> wrote:
>
>> On 02/18/2013 03:17 PM, William Colen wrote:
>>
>>> I suppose we can't use opennlp.apache.org to host it, can we?
>> We probably could somehow distribute it from Apache servers, but if we
>> can get it into the central maven repository it would also fix the issue
>> for the already
>> released OpenNLP versions as far as I know.
>>
>> Here is a guide which explains the process:
>> https://docs.sonatype.org/**display/Repository/Uploading+**
>> 3rd-party+Artifacts+to+The+**Central+Repository<https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository>
>>
>> Jörn
>>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
We are using "jwnl" as groupid, I don't know if we can upload using this
groupid. The best would be to reflect the Java package, which is
net.didion.jwnl, or to follow the one used by 14. rc3, which
is net.sf.jwordnet.jwnl.
But changing the groupid would not help the already released OpenNLP
versions.
On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann <ko...@gmail.com> wrote:
> On 02/18/2013 03:17 PM, William Colen wrote:
>
>> I suppose we can't use opennlp.apache.org to host it, can we?
>>
>>
> We probably could somehow distribute it from Apache servers, but if we
> can get it into the central maven repository it would also fix the issue
> for the already
> released OpenNLP versions as far as I know.
>
> Here is a guide which explains the process:
> https://docs.sonatype.org/**display/Repository/Uploading+**
> 3rd-party+Artifacts+to+The+**Central+Repository<https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository>
>
> Jörn
>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/18/2013 03:17 PM, William Colen wrote:
> I suppose we can't use opennlp.apache.org to host it, can we?
>
We probably could somehow distribute it from Apache servers, but if we
can get it into the central maven repository it would also fix the issue
for the already
released OpenNLP versions as far as I know.
Here is a guide which explains the process:
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
Jörn
Re: Next release
Posted by William Colen <wi...@gmail.com>.
I suppose we can't use opennlp.apache.org to host it, can we?
On Mon, Feb 18, 2013 at 10:57 AM, Jörn Kottmann <ko...@gmail.com> wrote:
> On 02/18/2013 02:07 AM, Lance Norskog wrote:
>
>> OPENNLP-510 Maven dependency on jwnl is broken
>>
>> The version of JWNL used in coreference does not have an available
>> Maven download. This made it hard to add OpenNLP to the Lucene/Solr
>> project.
>>
>> That project made a final (abandonment) release that is in Maven.
>> http://search.maven.org/#**artifactdetails%7Cnet.sf.**
>> jwordnet%7Cjwnl%7C1.4_rc3%**7Cjar<http://search.maven.org/#artifactdetails%7Cnet.sf.jwordnet%7Cjwnl%7C1.4_rc3%7Cjar>
>>
>>
>> Are there any coref users out there? Could you please check if this
>> version works?
>>
>
> The dependency is hosted in the maven repository on SourceForge, so it
> should be possible
> to get the 1.3 dependency automatically. From time to time this site gets
> too much traffic
> and is blocked, which makes the build unreliable.
>
> We shouldn't update to a newer version just for the sake of solving the
> repository problem,
> we could instead just create a new repository somewhere else or try to get
> it into an existing one.
>
> Jörn
>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/18/2013 02:07 AM, Lance Norskog wrote:
> OPENNLP-510 Maven dependency on jwnl is broken
>
> The version of JWNL used in coreference does not have an available
> Maven download. This made it hard to add OpenNLP to the Lucene/Solr
> project.
>
> That project made a final (abandonment) release that is in Maven.
> http://search.maven.org/#artifactdetails%7Cnet.sf.jwordnet%7Cjwnl%7C1.4_rc3%7Cjar
>
>
> Are there any coref users out there? Could you please check if this
> version works?
The dependency is hosted in the maven repository on SourceForge, so it
should be possible
to get the 1.3 dependency automatically. From time to time this site
gets too much traffic
and is blocked, which makes the build unreliable.
We shouldn't update to a newer version just for the sake of solving the
repository problem,
we could instead just create a new repository somewhere else or try to
get it into an existing one.
Jörn
Re: Next release
Posted by Lance Norskog <go...@gmail.com>.
OPENNLP-510 Maven dependency on jwnl is broken
The version of JWNL used in coreference does not have an available Maven
download. This made it hard to add OpenNLP to the Lucene/Solr project.
That project made a final (abandonment) release that is in Maven.
http://search.maven.org/#artifactdetails%7Cnet.sf.jwordnet%7Cjwnl%7C1.4_rc3%7Cjar
Are there any coref users out there? Could you please check if this
version works?
On 12/19/2012 12:17 PM, Jörn Kottmann wrote:
> Lets start to get the release done, are there any issues expect the
> two open
> ones which need to go into this release ?
>
> Open issues are:
> OPENNLP-541 Improve ADChunkSampleStream
> OPENNLP-402 CLI tools and formats refactored
>
> Jörn
>
> On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
>> Hi all,
>>
>> it has been a while since we released 1.5.2 and to me it looks
>> like its time for 1.5.3. I usually work now with the trunk version
>> because it just contain too many fixes I need for my day job.
>>
>> I will volunteer to be release manager if nobody else wants to
>> take this role.
>>
>> Any opinions?
>>
>> Jörn
>
Re: Next release
Posted by Jason Baldridge <ja...@gmail.com>.
+1
On Thu, Feb 14, 2013 at 6:31 AM, William Colen <wi...@gmail.com>wrote:
> Hi!!
>
> I can be the Release Manager for 1.5.3. It would be nice because Jörn was
> the Release Manager for all the other releases and we should have other
> members of the team familiar with the process.
>
> I would like to candidate myself as the Release Manager for 1.5.3. I will
> start building our first RC with Jörn supervision soon.
>
> Thank you,
> William
>
> On Wed, Dec 19, 2012 at 6:17 PM, Jörn Kottmann <ko...@gmail.com> wrote:
>
> > Lets start to get the release done, are there any issues expect the two
> > open
> > ones which need to go into this release ?
> >
> > Open issues are:
> > OPENNLP-541 Improve ADChunkSampleStream
> > OPENNLP-402 CLI tools and formats refactored
> >
> > Jörn
> >
> >
> > On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
> >
> >> Hi all,
> >>
> >> it has been a while since we released 1.5.2 and to me it looks
> >> like its time for 1.5.3. I usually work now with the trunk version
> >> because it just contain too many fixes I need for my day job.
> >>
> >> I will volunteer to be release manager if nobody else wants to
> >> take this role.
> >>
> >> Any opinions?
> >>
> >> Jörn
> >>
> >
> >
>
--
Jason Baldridge
Associate Professor, Department of Linguistics
The University of Texas at Austin
http://www.jasonbaldridge.com
http://twitter.com/jasonbaldridge
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
We will probably soon hear how it works for William, as far as I know
it should just work if the repository is set up in the settings.xml.
The attachment got removed by the mailing list server.
Jörn
On 02/15/2013 05:31 AM, Boris Galitsky wrote:
> Hi William
> It is a separate project which has its own structure, similar to opennlp.tools . Its pom.xml is working, creating an artifact, but has some kind of security issue uploading it to apache server. The idea was to try to do it in parallel with 1.5.3.
> I am attaching the pom.xml for your information
> RegardsBoris
>
>
>
>
>
>> From: william.colen@gmail.com
>> Date: Thu, 14 Feb 2013 18:41:59 -0200
>> Subject: Re: Next release
>> To: dev@opennlp.apache.org
>>
>> Hi, Boris,
>>
>> What i s the issue with the Similarity component? Is it part of the Maxent
>> + Tools release?
>>
>> Thank you,
>> William
>>
>>
>>
>> On Thu, Feb 14, 2013 at 12:06 PM, Boris Galitsky <bg...@hotmail.com>wrote:
>>
>>> It would be great if we can identify the problem in how to finish the
>>> release of 'similarity'.
>>> RegardsBoris
>>>
>>>
>>>
>>>
>>>
>>>> Date: Thu, 14 Feb 2013 13:57:06 +0100
>>>> From: kottmann@gmail.com
>>>> To: dev@opennlp.apache.org
>>>> Subject: Re: Next release
>>>>
>>>> On 02/14/2013 01:31 PM, William Colen wrote:
>>>>> I can be the Release Manager for 1.5.3. It would be nice because Jörn
>>> was
>>>>> the Release Manager for all the other releases and we should have other
>>>>> members of the team familiar with the process.
>>>>>
>>>>> I would like to candidate myself as the Release Manager for 1.5.3. I
>>> will
>>>>> start building our first RC with Jörn supervision soon.
>>>> +1 thanks. Its an important step for the project to distribute the
>>>> knowledge of
>>>> how to make a release.
>>>>
>>>> Jörn
>>>
>
RE: Next release
Posted by Boris Galitsky <bg...@hotmail.com>.
Hi William
It is a separate project which has its own structure, similar to opennlp.tools . Its pom.xml is working, creating an artifact, but has some kind of security issue uploading it to apache server. The idea was to try to do it in parallel with 1.5.3.
I am attaching the pom.xml for your information
RegardsBoris
> From: william.colen@gmail.com
> Date: Thu, 14 Feb 2013 18:41:59 -0200
> Subject: Re: Next release
> To: dev@opennlp.apache.org
>
> Hi, Boris,
>
> What i s the issue with the Similarity component? Is it part of the Maxent
> + Tools release?
>
> Thank you,
> William
>
>
>
> On Thu, Feb 14, 2013 at 12:06 PM, Boris Galitsky <bg...@hotmail.com>wrote:
>
> > It would be great if we can identify the problem in how to finish the
> > release of 'similarity'.
> > RegardsBoris
> >
> >
> >
> >
> >
> > > Date: Thu, 14 Feb 2013 13:57:06 +0100
> > > From: kottmann@gmail.com
> > > To: dev@opennlp.apache.org
> > > Subject: Re: Next release
> > >
> > > On 02/14/2013 01:31 PM, William Colen wrote:
> > > > I can be the Release Manager for 1.5.3. It would be nice because Jörn
> > was
> > > > the Release Manager for all the other releases and we should have other
> > > > members of the team familiar with the process.
> > > >
> > > > I would like to candidate myself as the Release Manager for 1.5.3. I
> > will
> > > > start building our first RC with Jörn supervision soon.
> > >
> > > +1 thanks. Its an important step for the project to distribute the
> > > knowledge of
> > > how to make a release.
> > >
> > > Jörn
> >
> >
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Hi, Boris,
What i s the issue with the Similarity component? Is it part of the Maxent
+ Tools release?
Thank you,
William
On Thu, Feb 14, 2013 at 12:06 PM, Boris Galitsky <bg...@hotmail.com>wrote:
> It would be great if we can identify the problem in how to finish the
> release of 'similarity'.
> RegardsBoris
>
>
>
>
>
> > Date: Thu, 14 Feb 2013 13:57:06 +0100
> > From: kottmann@gmail.com
> > To: dev@opennlp.apache.org
> > Subject: Re: Next release
> >
> > On 02/14/2013 01:31 PM, William Colen wrote:
> > > I can be the Release Manager for 1.5.3. It would be nice because Jörn
> was
> > > the Release Manager for all the other releases and we should have other
> > > members of the team familiar with the process.
> > >
> > > I would like to candidate myself as the Release Manager for 1.5.3. I
> will
> > > start building our first RC with Jörn supervision soon.
> >
> > +1 thanks. Its an important step for the project to distribute the
> > knowledge of
> > how to make a release.
> >
> > Jörn
>
>
RE: Next release
Posted by Boris Galitsky <bg...@hotmail.com>.
It would be great if we can identify the problem in how to finish the release of 'similarity'.
RegardsBoris
> Date: Thu, 14 Feb 2013 13:57:06 +0100
> From: kottmann@gmail.com
> To: dev@opennlp.apache.org
> Subject: Re: Next release
>
> On 02/14/2013 01:31 PM, William Colen wrote:
> > I can be the Release Manager for 1.5.3. It would be nice because Jörn was
> > the Release Manager for all the other releases and we should have other
> > members of the team familiar with the process.
> >
> > I would like to candidate myself as the Release Manager for 1.5.3. I will
> > start building our first RC with Jörn supervision soon.
>
> +1 thanks. Its an important step for the project to distribute the
> knowledge of
> how to make a release.
>
> Jörn
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 02/14/2013 01:31 PM, William Colen wrote:
> I can be the Release Manager for 1.5.3. It would be nice because Jörn was
> the Release Manager for all the other releases and we should have other
> members of the team familiar with the process.
>
> I would like to candidate myself as the Release Manager for 1.5.3. I will
> start building our first RC with Jörn supervision soon.
+1 thanks. Its an important step for the project to distribute the
knowledge of
how to make a release.
Jörn
Re: Next release
Posted by Aliaksandr Autayeu <al...@autayeu.com>.
+1! Well said.
Aliaksandr
On Thu, Feb 14, 2013 at 1:31 PM, William Colen <wi...@gmail.com>wrote:
> Hi!!
>
> I can be the Release Manager for 1.5.3. It would be nice because Jörn was
> the Release Manager for all the other releases and we should have other
> members of the team familiar with the process.
>
> I would like to candidate myself as the Release Manager for 1.5.3. I will
> start building our first RC with Jörn supervision soon.
>
> Thank you,
> William
>
> On Wed, Dec 19, 2012 at 6:17 PM, Jörn Kottmann <ko...@gmail.com> wrote:
>
> > Lets start to get the release done, are there any issues expect the two
> > open
> > ones which need to go into this release ?
> >
> > Open issues are:
> > OPENNLP-541 Improve ADChunkSampleStream
> > OPENNLP-402 CLI tools and formats refactored
> >
> > Jörn
> >
> >
> > On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
> >
> >> Hi all,
> >>
> >> it has been a while since we released 1.5.2 and to me it looks
> >> like its time for 1.5.3. I usually work now with the trunk version
> >> because it just contain too many fixes I need for my day job.
> >>
> >> I will volunteer to be release manager if nobody else wants to
> >> take this role.
> >>
> >> Any opinions?
> >>
> >> Jörn
> >>
> >
> >
>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Hi!!
I can be the Release Manager for 1.5.3. It would be nice because Jörn was
the Release Manager for all the other releases and we should have other
members of the team familiar with the process.
I would like to candidate myself as the Release Manager for 1.5.3. I will
start building our first RC with Jörn supervision soon.
Thank you,
William
On Wed, Dec 19, 2012 at 6:17 PM, Jörn Kottmann <ko...@gmail.com> wrote:
> Lets start to get the release done, are there any issues expect the two
> open
> ones which need to go into this release ?
>
> Open issues are:
> OPENNLP-541 Improve ADChunkSampleStream
> OPENNLP-402 CLI tools and formats refactored
>
> Jörn
>
>
> On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
>
>> Hi all,
>>
>> it has been a while since we released 1.5.2 and to me it looks
>> like its time for 1.5.3. I usually work now with the trunk version
>> because it just contain too many fixes I need for my day job.
>>
>> I will volunteer to be release manager if nobody else wants to
>> take this role.
>>
>> Any opinions?
>>
>> Jörn
>>
>
>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
Lets start to get the release done, are there any issues expect the two open
ones which need to go into this release ?
Open issues are:
OPENNLP-541 Improve ADChunkSampleStream
OPENNLP-402 CLI tools and formats refactored
Jörn
On 09/12/2012 03:56 PM, Jörn Kottmann wrote:
> Hi all,
>
> it has been a while since we released 1.5.2 and to me it looks
> like its time for 1.5.3. I usually work now with the trunk version
> because it just contain too many fixes I need for my day job.
>
> I will volunteer to be release manager if nobody else wants to
> take this role.
>
> Any opinions?
>
> Jörn
Re: Next release
Posted by "Jim - FooBar();" <ji...@gmail.com>.
On 12/09/12 16:33, Jörn Kottmann wrote:
> The patch attached to OPENNLP-496 could not be applied because it
> did not match the trunk version and we did not receive a follow up patch
> which solves this problem.
it doesn't match the trunk version simply because it has been named
DictionaryNameFinder2 instead of DictionaryNameFinder (wanted to keep
both versions around)...anyway it's been almost 6 months since then and
I'm not sure I can go back to that code any time soon...I did spend
quite a bit of time back then but now I don't have that much free time -
especially since, my private OPENNLP build which includes both the
AggregateNameFinder and the DictionaryNameFinder2 (which can accept as
many physical dictionaries as you like) has worked like a charm on at
least 3 big corpora so far...I'm not saying I've given up, but rather
that I really cannot pursue this at the moment...perhaps, if 1.5.3
breaks what I've done so far in my private build, I'll find some time to
fix it again so at least it works for me...but again I will most likely
follow the same rationale which you seem to disagree with.
Jim
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
The patches attached to these two issues are not ready
for inclusion.
For OPENNLP-494 we did not reach consensus on the implementation.
The patch attached to OPENNLP-496 could not be applied because it
did not match the trunk version and we did not receive a follow up patch
which solves this problem.
If you want to get these two issues fixed for 1.5.3 please provide us with
new patches which can be committed.
Thanks,
Jörn
On 09/12/2012 05:20 PM, Jim foo.bar wrote:
> Are you guys not considering the killer feature of merging results
> from several name-finders? see OPENNLP-494, OPENNLP-496...
>
> It's been working ike a charm for me...
>
>
>
> On 12/09/12 16:10, Jörn Kottmann wrote:
>> Are there any other features/fixes someone would like
>> to get into the release?
>>
>> Jörn
>>
>> On 09/12/2012 04:07 PM, William Colen wrote:
>>> Yes, I am also using the trunk for my projects as well.
>>>
>>> I still need to implement the customization factory for the chunker.
>>> It is
>>> important to me to have it in the next release. I will start working
>>> on it
>>> today and it should be ready by the end of the week.
>>>
>>> Thanks
>>> William
>>>
>>> On Wed, Sep 12, 2012 at 10:56 AM, Jörn Kottmann <ko...@gmail.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> it has been a while since we released 1.5.2 and to me it looks
>>>> like its time for 1.5.3. I usually work now with the trunk version
>>>> because it just contain too many fixes I need for my day job.
>>>>
>>>> I will volunteer to be release manager if nobody else wants to
>>>> take this role.
>>>>
>>>> Any opinions?
>>>>
>>>> Jörn
>>>>
>>
>
Re: Next release
Posted by "Jim foo.bar" <ji...@gmail.com>.
Are you guys not considering the killer feature of merging results from
several name-finders? see OPENNLP-494, OPENNLP-496...
It's been working ike a charm for me...
On 12/09/12 16:10, Jörn Kottmann wrote:
> Are there any other features/fixes someone would like
> to get into the release?
>
> Jörn
>
> On 09/12/2012 04:07 PM, William Colen wrote:
>> Yes, I am also using the trunk for my projects as well.
>>
>> I still need to implement the customization factory for the chunker.
>> It is
>> important to me to have it in the next release. I will start working
>> on it
>> today and it should be ready by the end of the week.
>>
>> Thanks
>> William
>>
>> On Wed, Sep 12, 2012 at 10:56 AM, Jörn Kottmann <ko...@gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> it has been a while since we released 1.5.2 and to me it looks
>>> like its time for 1.5.3. I usually work now with the trunk version
>>> because it just contain too many fixes I need for my day job.
>>>
>>> I will volunteer to be release manager if nobody else wants to
>>> take this role.
>>>
>>> Any opinions?
>>>
>>> Jörn
>>>
>
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
Are there any other features/fixes someone would like
to get into the release?
Jörn
On 09/12/2012 04:07 PM, William Colen wrote:
> Yes, I am also using the trunk for my projects as well.
>
> I still need to implement the customization factory for the chunker. It is
> important to me to have it in the next release. I will start working on it
> today and it should be ready by the end of the week.
>
> Thanks
> William
>
> On Wed, Sep 12, 2012 at 10:56 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>
>> Hi all,
>>
>> it has been a while since we released 1.5.2 and to me it looks
>> like its time for 1.5.3. I usually work now with the trunk version
>> because it just contain too many fixes I need for my day job.
>>
>> I will volunteer to be release manager if nobody else wants to
>> take this role.
>>
>> Any opinions?
>>
>> Jörn
>>
Re: Next release
Posted by James Kosin <ja...@gmail.com>.
On 9/18/2012 7:48 PM, James Kosin wrote:
> On 9/12/2012 10:48 AM, Jörn Kottmann wrote:
>> On 09/12/2012 04:07 PM, William Colen wrote:
>>> I still need to implement the customization factory for the chunker.
>>> It is
>>> important to me to have it in the next release. I will start working
>>> on it
>>> today and it should be ready by the end of the week.
>> I will be away for two weeks and then we need to work trough
>> the still open issues. We will probably have the first release candidate
>> in late October.
>>
>> Jörn
> I'm in the midst of doing a preliminary test on the current trunk to see
> what the changes do to the testing.
>
> I'll let you know the results when they get tallied.
>
> James
It is looking good so far. I'll have to redo later... just couldn't
wait all night for my computer to come back. Testing takes a long time.
James
RE: My colleagues and I verified Similarity component is working
and passing tests
Posted by Boris Galitsky <bg...@hotmail.com>.
Hi Jörn
I am stuck with the deployment script, somewhere around the gpg bug http://jira.codehaus.org/browse/MGPG-9so that the processes hangs. I tried all options mentioned in the discussions for this ticket, but nothing worked
I keep trying.
RegardsBoris
> Date: Tue, 23 Oct 2012 13:13:24 +0200
> From: kottmann@gmail.com
> To: dev@opennlp.apache.org
> Subject: Re: My colleagues and I verified Similarity component is working and passing tests
>
> Hello,
>
> are you ready now to build a release candidate?
>
> Jörn
>
> On 10/09/2012 06:30 PM, Boris Galitsky wrote:
> > Hello
> > Just wanted to say we can proceed with the release of 'Similarity' component
> > RegardsBoris
>
Re: My colleagues and I verified Similarity component is working
and passing tests
Posted by Jörn Kottmann <ko...@gmail.com>.
Hello,
are you ready now to build a release candidate?
Jörn
On 10/09/2012 06:30 PM, Boris Galitsky wrote:
> Hello
> Just wanted to say we can proceed with the release of 'Similarity' component
> RegardsBoris
My colleagues and I verified Similarity component is working and
passing tests
Posted by Boris Galitsky <bg...@hotmail.com>.
Hello
Just wanted to say we can proceed with the release of 'Similarity' component
RegardsBoris
RE: to release Similarity component
Posted by Boris Galitsky <bg...@hotmail.com>.
Hello
All tests should run now, I've verified on a couple of machines other than my own
RegardsBoris
> Date: Tue, 2 Oct 2012 23:08:45 +0200
> From: kottmann@gmail.com
> To: dev@opennlp.apache.org
> Subject: Re: to release Similarity component
>
> Hello,
>
> started to look into the packaging issue, but I cannot build it cause
> of failing tests. The test should run trough before we release it.
>
> It looks like the test depend on our English models, I can for example
> get this exception:
> java.io.FileNotFoundException:
> /home/xyz/opennlp/sandbox/opennlp-similarity/src/test/resources/models/en-chunker.bin
> (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:137)
> at java.io.FileInputStream.<init>(FileInputStream.java:96)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.initializeChunker(ParserChunker2MatcherProcessor.java:658)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.<init>(ParserChunker2MatcherProcessor.java:119)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.getInstance(ParserChunker2MatcherProcessor.java:140)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessorTest.testGroupedPhrasesFormer(ParserChunker2MatcherProcessorTest.java:34)
>
>
> The models cannot be included in subversion or in the distribution
> because they are not
> AL 2.0 licensed. So we should not have tests depending on them.
>
> Can you fix this? In my opinion the tests should just use pre-annotated
> data and do not use
> any of our models to produce this data on the fly.
>
> Please get a fresh checkout of the opennlp-similarity folder, and try to
> get it build
> with mvn install. That needs to work out of the box. There were also
> other test failures,
> e.g. one where it could not parse a sentence.
>
> Jörn
>
> On 09/19/2012 11:57 PM, Boris Galitsky wrote:
> > Hi guys
> > I would like to complete this project.This tickets https://issues.apache.org/jira/browse/OPENNLP-497
> > is supposed to conclude it, I edited pom.xml and added files similar to what apache-opennlp-1.5.2-incubating-bin.zip has.
> > I manually formed the distribution archive and attached it to this ticket.
> > As an additional round of verification that Similarity is working, besides a number of application areas (which live in junits) I also built a SOLR search handler which re-rankssearch results according to similarity of parse trees for questions and answers. This way SOLR uses OpenNLP to improve search relevance (will create a ticket and add the request handler).
> > What are the next steps?
> > Best regardsBoris
>
RE: to release Similarity component
Posted by Boris Galitsky <bg...@hotmail.com>.
Hello all
I am caching parsing results in a csv file, and read this file if the models are not available. It all works locally, let me check out again and see if I can reproduce what you are reporting.
RegardsBoris
> Date: Tue, 2 Oct 2012 23:08:45 +0200
> From: kottmann@gmail.com
> To: dev@opennlp.apache.org
> Subject: Re: to release Similarity component
>
> Hello,
>
> started to look into the packaging issue, but I cannot build it cause
> of failing tests. The test should run trough before we release it.
>
> It looks like the test depend on our English models, I can for example
> get this exception:
> java.io.FileNotFoundException:
> /home/xyz/opennlp/sandbox/opennlp-similarity/src/test/resources/models/en-chunker.bin
> (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:137)
> at java.io.FileInputStream.<init>(FileInputStream.java:96)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.initializeChunker(ParserChunker2MatcherProcessor.java:658)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.<init>(ParserChunker2MatcherProcessor.java:119)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.getInstance(ParserChunker2MatcherProcessor.java:140)
> at
> opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessorTest.testGroupedPhrasesFormer(ParserChunker2MatcherProcessorTest.java:34)
>
>
> The models cannot be included in subversion or in the distribution
> because they are not
> AL 2.0 licensed. So we should not have tests depending on them.
>
> Can you fix this? In my opinion the tests should just use pre-annotated
> data and do not use
> any of our models to produce this data on the fly.
>
> Please get a fresh checkout of the opennlp-similarity folder, and try to
> get it build
> with mvn install. That needs to work out of the box. There were also
> other test failures,
> e.g. one where it could not parse a sentence.
>
> Jörn
>
> On 09/19/2012 11:57 PM, Boris Galitsky wrote:
> > Hi guys
> > I would like to complete this project.This tickets https://issues.apache.org/jira/browse/OPENNLP-497
> > is supposed to conclude it, I edited pom.xml and added files similar to what apache-opennlp-1.5.2-incubating-bin.zip has.
> > I manually formed the distribution archive and attached it to this ticket.
> > As an additional round of verification that Similarity is working, besides a number of application areas (which live in junits) I also built a SOLR search handler which re-rankssearch results according to similarity of parse trees for questions and answers. This way SOLR uses OpenNLP to improve search relevance (will create a ticket and add the request handler).
> > What are the next steps?
> > Best regardsBoris
>
Re: to release Similarity component
Posted by Jörn Kottmann <ko...@gmail.com>.
Hello,
started to look into the packaging issue, but I cannot build it cause
of failing tests. The test should run trough before we release it.
It looks like the test depend on our English models, I can for example
get this exception:
java.io.FileNotFoundException:
/home/xyz/opennlp/sandbox/opennlp-similarity/src/test/resources/models/en-chunker.bin
(No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:137)
at java.io.FileInputStream.<init>(FileInputStream.java:96)
at
opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.initializeChunker(ParserChunker2MatcherProcessor.java:658)
at
opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.<init>(ParserChunker2MatcherProcessor.java:119)
at
opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessor.getInstance(ParserChunker2MatcherProcessor.java:140)
at
opennlp.tools.textsimilarity.chunker2matcher.ParserChunker2MatcherProcessorTest.testGroupedPhrasesFormer(ParserChunker2MatcherProcessorTest.java:34)
The models cannot be included in subversion or in the distribution
because they are not
AL 2.0 licensed. So we should not have tests depending on them.
Can you fix this? In my opinion the tests should just use pre-annotated
data and do not use
any of our models to produce this data on the fly.
Please get a fresh checkout of the opennlp-similarity folder, and try to
get it build
with mvn install. That needs to work out of the box. There were also
other test failures,
e.g. one where it could not parse a sentence.
Jörn
On 09/19/2012 11:57 PM, Boris Galitsky wrote:
> Hi guys
> I would like to complete this project.This tickets https://issues.apache.org/jira/browse/OPENNLP-497
> is supposed to conclude it, I edited pom.xml and added files similar to what apache-opennlp-1.5.2-incubating-bin.zip has.
> I manually formed the distribution archive and attached it to this ticket.
> As an additional round of verification that Similarity is working, besides a number of application areas (which live in junits) I also built a SOLR search handler which re-rankssearch results according to similarity of parse trees for questions and answers. This way SOLR uses OpenNLP to improve search relevance (will create a ticket and add the request handler).
> What are the next steps?
> Best regardsBoris
to release Similarity component
Posted by Boris Galitsky <bg...@hotmail.com>.
Hi guys
I would like to complete this project.This tickets https://issues.apache.org/jira/browse/OPENNLP-497
is supposed to conclude it, I edited pom.xml and added files similar to what apache-opennlp-1.5.2-incubating-bin.zip has.
I manually formed the distribution archive and attached it to this ticket.
As an additional round of verification that Similarity is working, besides a number of application areas (which live in junits) I also built a SOLR search handler which re-rankssearch results according to similarity of parse trees for questions and answers. This way SOLR uses OpenNLP to improve search relevance (will create a ticket and add the request handler).
What are the next steps?
Best regardsBoris
Re: Next release
Posted by James Kosin <ja...@gmail.com>.
On 9/12/2012 10:48 AM, Jörn Kottmann wrote:
> On 09/12/2012 04:07 PM, William Colen wrote:
>> I still need to implement the customization factory for the chunker.
>> It is
>> important to me to have it in the next release. I will start working
>> on it
>> today and it should be ready by the end of the week.
>
> I will be away for two weeks and then we need to work trough
> the still open issues. We will probably have the first release candidate
> in late October.
>
> Jörn
I'm in the midst of doing a preliminary test on the current trunk to see
what the changes do to the testing.
I'll let you know the results when they get tallied.
James
Re: Next release
Posted by Jörn Kottmann <ko...@gmail.com>.
On 09/12/2012 04:07 PM, William Colen wrote:
> I still need to implement the customization factory for the chunker. It is
> important to me to have it in the next release. I will start working on it
> today and it should be ready by the end of the week.
I will be away for two weeks and then we need to work trough
the still open issues. We will probably have the first release candidate
in late October.
Jörn
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Yes, I am also using the trunk for my projects as well.
I still need to implement the customization factory for the chunker. It is
important to me to have it in the next release. I will start working on it
today and it should be ready by the end of the week.
Thanks
William
On Wed, Sep 12, 2012 at 10:56 AM, Jörn Kottmann <ko...@gmail.com> wrote:
> Hi all,
>
> it has been a while since we released 1.5.2 and to me it looks
> like its time for 1.5.3. I usually work now with the trunk version
> because it just contain too many fixes I need for my day job.
>
> I will volunteer to be release manager if nobody else wants to
> take this role.
>
> Any opinions?
>
> Jörn
>