You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Joern Kottmann <ko...@gmail.com> on 2016/11/07 17:59:00 UTC
Next release
Hello all,
since our last release it has been a while and we received quite a few
changes which would be nice to get released.
There are still some open Jira issues, but mostly smaller things that
can be wrapped up rather quickly.
Is there anything important missing which should go into the next
release? Otherwise I think we should also aim for more frequent
released and just make one again early next year, with all the stuff we
might miss out now.
We took in a patch - as part of OPENNLP-830 - to replace our self-made
hash table with the java.util.HashMap. This change is not backward
compatible for folks who extend AbstractModel.
Should we go with 1.6.1 as a next version or should we make 1.7.0 to
reflect that?
Previously we only had backward incompatible changes in versions which
bumped by the second number. Maybe that is better choice. It will
probably break some peoples code when they update.
We also have lots of deprecated API still in OpenNLP, should we try to
remove as much as possible of it now?
J�rn
Re: Next release
Posted by "Mattmann, Chris A (3010)" <ch...@jpl.nasa.gov>.
I’m fine with calling it 1.7.0.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010)
Manager, Open Source Projects Formulation and Development Office (8212)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 180-503E, Mailstop: 180-502
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On 11/7/16, 9:59 AM, "Joern Kottmann" <ko...@gmail.com> wrote:
Hello all,
since our last release it has been a while and we received quite a few
changes which would be nice to get released.
There are still some open Jira issues, but mostly smaller things that
can be wrapped up rather quickly.
Is there anything important missing which should go into the next
release? Otherwise I think we should also aim for more frequent
released and just make one again early next year, with all the stuff we
might miss out now.
We took in a patch - as part of OPENNLP-830 - to replace our self-made
hash table with the java.util.HashMap. This change is not backward
compatible for folks who extend AbstractModel.
Should we go with 1.6.1 as a next version or should we make 1.7.0 to
reflect that?
Previously we only had backward incompatible changes in versions which
bumped by the second number. Maybe that is better choice. It will
probably break some peoples code when they update.
We also have lots of deprecated API still in OpenNLP, should we try to
remove as much as possible of it now?
Jörn
Re: Next release
Posted by Tommaso Teofili <to...@gmail.com>.
+1 for 1.7
Il giorno lun 7 nov 2016 alle 19:27 William Colen <wi...@gmail.com>
ha scritto:
> +1 for 1.7
>
> William
>
> 2016-11-07 16:22 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
>
> > I am also in favor of 1.7.
> >
> > Jörn
> >
> > On Mon, 2016-11-07 at 18:01 +0000, Russ, Daniel (NIH/CIT) [E] wrote:
> > > Also the lemmatizer has significantly changed. I vote 1.7
> > >
> > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> > >
> > > Hello all,
> > >
> > > since our last release it has been a while and we received quite
> > > a few
> > > changes which would be nice to get released.
> > >
> > > There are still some open Jira issues, but mostly smaller things
> > > that
> > > can be wrapped up rather quickly.
> > >
> > > Is there anything important missing which should go into the next
> > > release? Otherwise I think we should also aim for more frequent
> > > released and just make one again early next year, with all the
> > > stuff we
> > > might miss out now.
> > >
> > > We took in a patch - as part of OPENNLP-830 - to replace our
> > > self-made
> > > hash table with the java.util.HashMap. This change is not
> > > backward
> > > compatible for folks who extend AbstractModel.
> > >
> > > Should we go with 1.6.1 as a next version or should we make 1.7.0
> > > to
> > > reflect that?
> > >
> > > Previously we only had backward incompatible changes in versions
> > > which
> > > bumped by the second number. Maybe that is better choice. It will
> > > probably break some peoples code when they update.
> > >
> > > We also have lots of deprecated API still in OpenNLP, should we
> > > try to
> > > remove as much as possible of it now?
> > >
> > > Jörn
> > >
> > >
> >
>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
+1 for 1.7
William
2016-11-07 16:22 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> I am also in favor of 1.7.
>
> Jörn
>
> On Mon, 2016-11-07 at 18:01 +0000, Russ, Daniel (NIH/CIT) [E] wrote:
> > Also the lemmatizer has significantly changed. I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> >
> > Hello all,
> >
> > since our last release it has been a while and we received quite
> > a few
> > changes which would be nice to get released.
> >
> > There are still some open Jira issues, but mostly smaller things
> > that
> > can be wrapped up rather quickly.
> >
> > Is there anything important missing which should go into the next
> > release? Otherwise I think we should also aim for more frequent
> > released and just make one again early next year, with all the
> > stuff we
> > might miss out now.
> >
> > We took in a patch - as part of OPENNLP-830 - to replace our
> > self-made
> > hash table with the java.util.HashMap. This change is not
> > backward
> > compatible for folks who extend AbstractModel.
> >
> > Should we go with 1.6.1 as a next version or should we make 1.7.0
> > to
> > reflect that?
> >
> > Previously we only had backward incompatible changes in versions
> > which
> > bumped by the second number. Maybe that is better choice. It will
> > probably break some peoples code when they update.
> >
> > We also have lots of deprecated API still in OpenNLP, should we
> > try to
> > remove as much as possible of it now?
> >
> > Jörn
> >
> >
>
Re: Next release
Posted by Joern Kottmann <ko...@gmail.com>.
I am also in favor of 1.7.
J�rn
On Mon, 2016-11-07 at 18:01 +0000, Russ, Daniel (NIH/CIT) [E] wrote:
> Also the lemmatizer has significantly changed.��I vote 1.7
>
> On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
>
> ����Hello all,
> ����
> ����since our last release it has been a while and we received quite
> a few
> ����changes which would be nice to get released.
> ����
> ����There are still some open Jira issues, but mostly smaller things
> that
> ����can be wrapped up rather quickly.
> ����
> ����Is there anything important missing which should go into the next
> ����release? Otherwise I think we should also aim for more frequent
> ����released and just make one again early next year, with all the
> stuff we
> ����might miss out now.
> ����
> ����We took in a patch - as part of OPENNLP-830 - to replace our
> self-made
> ����hash table with the java.util.HashMap. This change is not
> backward
> ����compatible for folks who extend AbstractModel.
> ����
> ����Should we go with 1.6.1 as a next version or should we make 1.7.0
> to
> ����reflect that?
> ����
> ����Previously we only had backward incompatible changes in versions
> which
> ����bumped by the second number. Maybe that is better choice. It will
> ����probably break some peoples code when they update.
> ����
> ����We also have lots of deprecated API still in OpenNLP, should we
> try to
> ����remove as much as possible of it now?
> ����
> ����J�rn
> ����
>
Re: Next release
Posted by Cohan Sujay Carlos <co...@aiaioo.com>.
Folks, I just noticed that the OpenNLP download links are broken (and so is
the Maven download).
To replicate the issue, go to http://opennlp.apache.org/download.html and
click on any of the download links.
Secondly, has the snapshot branch been named to 1.7.0, and does the Maven
instruction page http://opennlp.apache.org/maven-dependency.html need to be
updated?
It currently says:
OpenNLP Tools SNAPSHOT Dependency
<http://opennlp.apache.org/maven-dependency.html#opennlp-tools-snapshot-dependency>
To use the current trunk version define the following dependency:
<dependency>
<groupId>org.apache.opennlp</groupId>
<artifactId>opennlp-tools</artifactId>
<version>*1.6.1-SNAPSHOT*</version></dependency>
Cohan Sujay Carlos
Aiaioo Labs, +91-77605-80015, http://www.aiaioo.com
On Wed, Nov 23, 2016 at 5:36 PM, Rodrigo Agerri <ra...@apache.org> wrote:
> Hello,
>
> I have added the lemmatizer info to RELEASE in opennlp-distr. Commit
> pushed to new branch 889.
>
> Rodrigo
>
> R
>
> On Thu, Nov 10, 2016 at 11:42 AM, William Colen <wi...@gmail.com>
> wrote:
> > Cool. There is a lot of PlainTextByLineStream references in deprecated
> > methods, specially main methods. I will ignore them and you can remove
> the
> > main method when you go through each tool.
> > I will focus on PlainTextByLineStream that are not inside deprecated
> > methods.
> >
> >
> > 2016-11-10 6:39 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> >
> >> Ok, I created a couple of issues and will go through them rather
> quickly.
> >>
> >> Jörn
> >>
> >> On Thu, Nov 10, 2016 at 3:36 AM, William Colen <william.colen@gmail.com
> >
> >> wrote:
> >>
> >> > Jörn, I can help removing deprecated code. I started with
> >> > PlainTextByLineStream. It is used everywhere so there is a lot to
> change.
> >> >
> >> >
> >> > 2016-11-08 9:08 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> >> >
> >> > > I suggest we remove more deprecated code, there is still a lot which
> >> > could
> >> > > be removed and is really old.
> >> > > It is a bit of a boring task, if anyone has some spare cycles help
> >> would
> >> > be
> >> > > welcome.
> >> > >
> >> > > Jörn
> >> > >
> >> > > On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <
> >> > aliaksandr@autayeu.com
> >> > > >
> >> > > wrote:
> >> > >
> >> > > > +1 for 1.7 (also due to lemmatized changes and removal of
> deprecated
> >> > > code).
> >> > > >
> >> > > > On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org>
> >> > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > >
> >> > > > > +1 1.7.0 in next release and +1 for a yearly release
> >> > > > >
> >> > > > > Just to provide some info, the main changes in the lemmatizer
> have
> >> > > been:
> >> > > > >
> >> > > > > 1. Added a supervised statistical lemmatizer, usable from the
> CLI
> >> and
> >> > > > > API. The supervised lemmaitzer now provides a much better
> coverage
> >> > for
> >> > > > > unknown words with respect to the previously existing
> >> > dictionary-based
> >> > > > > one.
> >> > > > > 2. The lemmatizer component has been rewritten and the API
> >> therefore
> >> > > > > has substantially changed. Thus, the changes in the
> >> Dictionary-based
> >> > > > > lemmatizer are not backward compatible. In any case, I do not
> think
> >> > > > > that so many people was using it and the change at using the
> API is
> >> > > > > minor.
> >> > > > >
> >> > > > > The new statistical lemmatizer can support the Dictionary-based
> >> > > > > lemmatizers often used to provide features for components such
> as
> >> > Word
> >> > > > > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In
> >> this
> >> > > > > regard, it will be nice to aim at working on the development of
> >> those
> >> > > > > two components for their release. Maybe the next release is too
> >> > close,
> >> > > > > but definitely for the next one.
> >> > > > >
> >> > > > > Cheers,
> >> > > > >
> >> > > > > Rodrigo
> >> > > > >
> >> > > > > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> >> > > > > <dr...@mail.nih.gov> wrote:
> >> > > > > > Also the lemmatizer has significantly changed. I vote 1.7
> >> > > > > >
> >> > > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com>
> >> wrote:
> >> > > > > >
> >> > > > > > Hello all,
> >> > > > > >
> >> > > > > > since our last release it has been a while and we received
> >> > quite
> >> > > a
> >> > > > > few
> >> > > > > > changes which would be nice to get released.
> >> > > > > >
> >> > > > > > There are still some open Jira issues, but mostly smaller
> >> > things
> >> > > > that
> >> > > > > > can be wrapped up rather quickly.
> >> > > > > >
> >> > > > > > Is there anything important missing which should go into
> the
> >> > next
> >> > > > > > release? Otherwise I think we should also aim for more
> >> frequent
> >> > > > > > released and just make one again early next year, with all
> >> the
> >> > > > stuff
> >> > > > > we
> >> > > > > > might miss out now.
> >> > > > > >
> >> > > > > > We took in a patch - as part of OPENNLP-830 - to replace
> our
> >> > > > > self-made
> >> > > > > > hash table with the java.util.HashMap. This change is not
> >> > > backward
> >> > > > > > compatible for folks who extend AbstractModel.
> >> > > > > >
> >> > > > > > Should we go with 1.6.1 as a next version or should we
> make
> >> > 1.7.0
> >> > > > to
> >> > > > > > reflect that?
> >> > > > > >
> >> > > > > > Previously we only had backward incompatible changes in
> >> > versions
> >> > > > > which
> >> > > > > > bumped by the second number. Maybe that is better choice.
> It
> >> > will
> >> > > > > > probably break some peoples code when they update.
> >> > > > > >
> >> > > > > > We also have lots of deprecated API still in OpenNLP,
> should
> >> we
> >> > > try
> >> > > > > to
> >> > > > > > remove as much as possible of it now?
> >> > > > > >
> >> > > > > > Jörn
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>
Re: Next release
Posted by Rodrigo Agerri <ra...@apache.org>.
Hello,
I have added the lemmatizer info to RELEASE in opennlp-distr. Commit
pushed to new branch 889.
Rodrigo
R
On Thu, Nov 10, 2016 at 11:42 AM, William Colen <wi...@gmail.com> wrote:
> Cool. There is a lot of PlainTextByLineStream references in deprecated
> methods, specially main methods. I will ignore them and you can remove the
> main method when you go through each tool.
> I will focus on PlainTextByLineStream that are not inside deprecated
> methods.
>
>
> 2016-11-10 6:39 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
>
>> Ok, I created a couple of issues and will go through them rather quickly.
>>
>> Jörn
>>
>> On Thu, Nov 10, 2016 at 3:36 AM, William Colen <wi...@gmail.com>
>> wrote:
>>
>> > Jörn, I can help removing deprecated code. I started with
>> > PlainTextByLineStream. It is used everywhere so there is a lot to change.
>> >
>> >
>> > 2016-11-08 9:08 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
>> >
>> > > I suggest we remove more deprecated code, there is still a lot which
>> > could
>> > > be removed and is really old.
>> > > It is a bit of a boring task, if anyone has some spare cycles help
>> would
>> > be
>> > > welcome.
>> > >
>> > > Jörn
>> > >
>> > > On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <
>> > aliaksandr@autayeu.com
>> > > >
>> > > wrote:
>> > >
>> > > > +1 for 1.7 (also due to lemmatized changes and removal of deprecated
>> > > code).
>> > > >
>> > > > On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org>
>> > wrote:
>> > > >
>> > > > > Hello,
>> > > > >
>> > > > > +1 1.7.0 in next release and +1 for a yearly release
>> > > > >
>> > > > > Just to provide some info, the main changes in the lemmatizer have
>> > > been:
>> > > > >
>> > > > > 1. Added a supervised statistical lemmatizer, usable from the CLI
>> and
>> > > > > API. The supervised lemmaitzer now provides a much better coverage
>> > for
>> > > > > unknown words with respect to the previously existing
>> > dictionary-based
>> > > > > one.
>> > > > > 2. The lemmatizer component has been rewritten and the API
>> therefore
>> > > > > has substantially changed. Thus, the changes in the
>> Dictionary-based
>> > > > > lemmatizer are not backward compatible. In any case, I do not think
>> > > > > that so many people was using it and the change at using the API is
>> > > > > minor.
>> > > > >
>> > > > > The new statistical lemmatizer can support the Dictionary-based
>> > > > > lemmatizers often used to provide features for components such as
>> > Word
>> > > > > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In
>> this
>> > > > > regard, it will be nice to aim at working on the development of
>> those
>> > > > > two components for their release. Maybe the next release is too
>> > close,
>> > > > > but definitely for the next one.
>> > > > >
>> > > > > Cheers,
>> > > > >
>> > > > > Rodrigo
>> > > > >
>> > > > > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
>> > > > > <dr...@mail.nih.gov> wrote:
>> > > > > > Also the lemmatizer has significantly changed. I vote 1.7
>> > > > > >
>> > > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com>
>> wrote:
>> > > > > >
>> > > > > > Hello all,
>> > > > > >
>> > > > > > since our last release it has been a while and we received
>> > quite
>> > > a
>> > > > > few
>> > > > > > changes which would be nice to get released.
>> > > > > >
>> > > > > > There are still some open Jira issues, but mostly smaller
>> > things
>> > > > that
>> > > > > > can be wrapped up rather quickly.
>> > > > > >
>> > > > > > Is there anything important missing which should go into the
>> > next
>> > > > > > release? Otherwise I think we should also aim for more
>> frequent
>> > > > > > released and just make one again early next year, with all
>> the
>> > > > stuff
>> > > > > we
>> > > > > > might miss out now.
>> > > > > >
>> > > > > > We took in a patch - as part of OPENNLP-830 - to replace our
>> > > > > self-made
>> > > > > > hash table with the java.util.HashMap. This change is not
>> > > backward
>> > > > > > compatible for folks who extend AbstractModel.
>> > > > > >
>> > > > > > Should we go with 1.6.1 as a next version or should we make
>> > 1.7.0
>> > > > to
>> > > > > > reflect that?
>> > > > > >
>> > > > > > Previously we only had backward incompatible changes in
>> > versions
>> > > > > which
>> > > > > > bumped by the second number. Maybe that is better choice. It
>> > will
>> > > > > > probably break some peoples code when they update.
>> > > > > >
>> > > > > > We also have lots of deprecated API still in OpenNLP, should
>> we
>> > > try
>> > > > > to
>> > > > > > remove as much as possible of it now?
>> > > > > >
>> > > > > > Jörn
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Cool. There is a lot of PlainTextByLineStream references in deprecated
methods, specially main methods. I will ignore them and you can remove the
main method when you go through each tool.
I will focus on PlainTextByLineStream that are not inside deprecated
methods.
2016-11-10 6:39 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> Ok, I created a couple of issues and will go through them rather quickly.
>
> Jörn
>
> On Thu, Nov 10, 2016 at 3:36 AM, William Colen <wi...@gmail.com>
> wrote:
>
> > Jörn, I can help removing deprecated code. I started with
> > PlainTextByLineStream. It is used everywhere so there is a lot to change.
> >
> >
> > 2016-11-08 9:08 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> >
> > > I suggest we remove more deprecated code, there is still a lot which
> > could
> > > be removed and is really old.
> > > It is a bit of a boring task, if anyone has some spare cycles help
> would
> > be
> > > welcome.
> > >
> > > Jörn
> > >
> > > On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <
> > aliaksandr@autayeu.com
> > > >
> > > wrote:
> > >
> > > > +1 for 1.7 (also due to lemmatized changes and removal of deprecated
> > > code).
> > > >
> > > > On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org>
> > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > +1 1.7.0 in next release and +1 for a yearly release
> > > > >
> > > > > Just to provide some info, the main changes in the lemmatizer have
> > > been:
> > > > >
> > > > > 1. Added a supervised statistical lemmatizer, usable from the CLI
> and
> > > > > API. The supervised lemmaitzer now provides a much better coverage
> > for
> > > > > unknown words with respect to the previously existing
> > dictionary-based
> > > > > one.
> > > > > 2. The lemmatizer component has been rewritten and the API
> therefore
> > > > > has substantially changed. Thus, the changes in the
> Dictionary-based
> > > > > lemmatizer are not backward compatible. In any case, I do not think
> > > > > that so many people was using it and the change at using the API is
> > > > > minor.
> > > > >
> > > > > The new statistical lemmatizer can support the Dictionary-based
> > > > > lemmatizers often used to provide features for components such as
> > Word
> > > > > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In
> this
> > > > > regard, it will be nice to aim at working on the development of
> those
> > > > > two components for their release. Maybe the next release is too
> > close,
> > > > > but definitely for the next one.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Rodrigo
> > > > >
> > > > > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> > > > > <dr...@mail.nih.gov> wrote:
> > > > > > Also the lemmatizer has significantly changed. I vote 1.7
> > > > > >
> > > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com>
> wrote:
> > > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > since our last release it has been a while and we received
> > quite
> > > a
> > > > > few
> > > > > > changes which would be nice to get released.
> > > > > >
> > > > > > There are still some open Jira issues, but mostly smaller
> > things
> > > > that
> > > > > > can be wrapped up rather quickly.
> > > > > >
> > > > > > Is there anything important missing which should go into the
> > next
> > > > > > release? Otherwise I think we should also aim for more
> frequent
> > > > > > released and just make one again early next year, with all
> the
> > > > stuff
> > > > > we
> > > > > > might miss out now.
> > > > > >
> > > > > > We took in a patch - as part of OPENNLP-830 - to replace our
> > > > > self-made
> > > > > > hash table with the java.util.HashMap. This change is not
> > > backward
> > > > > > compatible for folks who extend AbstractModel.
> > > > > >
> > > > > > Should we go with 1.6.1 as a next version or should we make
> > 1.7.0
> > > > to
> > > > > > reflect that?
> > > > > >
> > > > > > Previously we only had backward incompatible changes in
> > versions
> > > > > which
> > > > > > bumped by the second number. Maybe that is better choice. It
> > will
> > > > > > probably break some peoples code when they update.
> > > > > >
> > > > > > We also have lots of deprecated API still in OpenNLP, should
> we
> > > try
> > > > > to
> > > > > > remove as much as possible of it now?
> > > > > >
> > > > > > Jörn
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Next release
Posted by Joern Kottmann <ko...@gmail.com>.
Ok, I created a couple of issues and will go through them rather quickly.
Jörn
On Thu, Nov 10, 2016 at 3:36 AM, William Colen <wi...@gmail.com>
wrote:
> Jörn, I can help removing deprecated code. I started with
> PlainTextByLineStream. It is used everywhere so there is a lot to change.
>
>
> 2016-11-08 9:08 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
>
> > I suggest we remove more deprecated code, there is still a lot which
> could
> > be removed and is really old.
> > It is a bit of a boring task, if anyone has some spare cycles help would
> be
> > welcome.
> >
> > Jörn
> >
> > On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <
> aliaksandr@autayeu.com
> > >
> > wrote:
> >
> > > +1 for 1.7 (also due to lemmatized changes and removal of deprecated
> > code).
> > >
> > > On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org>
> wrote:
> > >
> > > > Hello,
> > > >
> > > > +1 1.7.0 in next release and +1 for a yearly release
> > > >
> > > > Just to provide some info, the main changes in the lemmatizer have
> > been:
> > > >
> > > > 1. Added a supervised statistical lemmatizer, usable from the CLI and
> > > > API. The supervised lemmaitzer now provides a much better coverage
> for
> > > > unknown words with respect to the previously existing
> dictionary-based
> > > > one.
> > > > 2. The lemmatizer component has been rewritten and the API therefore
> > > > has substantially changed. Thus, the changes in the Dictionary-based
> > > > lemmatizer are not backward compatible. In any case, I do not think
> > > > that so many people was using it and the change at using the API is
> > > > minor.
> > > >
> > > > The new statistical lemmatizer can support the Dictionary-based
> > > > lemmatizers often used to provide features for components such as
> Word
> > > > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> > > > regard, it will be nice to aim at working on the development of those
> > > > two components for their release. Maybe the next release is too
> close,
> > > > but definitely for the next one.
> > > >
> > > > Cheers,
> > > >
> > > > Rodrigo
> > > >
> > > > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> > > > <dr...@mail.nih.gov> wrote:
> > > > > Also the lemmatizer has significantly changed. I vote 1.7
> > > > >
> > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> > > > >
> > > > > Hello all,
> > > > >
> > > > > since our last release it has been a while and we received
> quite
> > a
> > > > few
> > > > > changes which would be nice to get released.
> > > > >
> > > > > There are still some open Jira issues, but mostly smaller
> things
> > > that
> > > > > can be wrapped up rather quickly.
> > > > >
> > > > > Is there anything important missing which should go into the
> next
> > > > > release? Otherwise I think we should also aim for more frequent
> > > > > released and just make one again early next year, with all the
> > > stuff
> > > > we
> > > > > might miss out now.
> > > > >
> > > > > We took in a patch - as part of OPENNLP-830 - to replace our
> > > > self-made
> > > > > hash table with the java.util.HashMap. This change is not
> > backward
> > > > > compatible for folks who extend AbstractModel.
> > > > >
> > > > > Should we go with 1.6.1 as a next version or should we make
> 1.7.0
> > > to
> > > > > reflect that?
> > > > >
> > > > > Previously we only had backward incompatible changes in
> versions
> > > > which
> > > > > bumped by the second number. Maybe that is better choice. It
> will
> > > > > probably break some peoples code when they update.
> > > > >
> > > > > We also have lots of deprecated API still in OpenNLP, should we
> > try
> > > > to
> > > > > remove as much as possible of it now?
> > > > >
> > > > > Jörn
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Next release
Posted by William Colen <wi...@gmail.com>.
Jörn, I can help removing deprecated code. I started with
PlainTextByLineStream. It is used everywhere so there is a lot to change.
2016-11-08 9:08 GMT-02:00 Joern Kottmann <ko...@gmail.com>:
> I suggest we remove more deprecated code, there is still a lot which could
> be removed and is really old.
> It is a bit of a boring task, if anyone has some spare cycles help would be
> welcome.
>
> Jörn
>
> On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <aliaksandr@autayeu.com
> >
> wrote:
>
> > +1 for 1.7 (also due to lemmatized changes and removal of deprecated
> code).
> >
> > On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org> wrote:
> >
> > > Hello,
> > >
> > > +1 1.7.0 in next release and +1 for a yearly release
> > >
> > > Just to provide some info, the main changes in the lemmatizer have
> been:
> > >
> > > 1. Added a supervised statistical lemmatizer, usable from the CLI and
> > > API. The supervised lemmaitzer now provides a much better coverage for
> > > unknown words with respect to the previously existing dictionary-based
> > > one.
> > > 2. The lemmatizer component has been rewritten and the API therefore
> > > has substantially changed. Thus, the changes in the Dictionary-based
> > > lemmatizer are not backward compatible. In any case, I do not think
> > > that so many people was using it and the change at using the API is
> > > minor.
> > >
> > > The new statistical lemmatizer can support the Dictionary-based
> > > lemmatizers often used to provide features for components such as Word
> > > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> > > regard, it will be nice to aim at working on the development of those
> > > two components for their release. Maybe the next release is too close,
> > > but definitely for the next one.
> > >
> > > Cheers,
> > >
> > > Rodrigo
> > >
> > > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> > > <dr...@mail.nih.gov> wrote:
> > > > Also the lemmatizer has significantly changed. I vote 1.7
> > > >
> > > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> > > >
> > > > Hello all,
> > > >
> > > > since our last release it has been a while and we received quite
> a
> > > few
> > > > changes which would be nice to get released.
> > > >
> > > > There are still some open Jira issues, but mostly smaller things
> > that
> > > > can be wrapped up rather quickly.
> > > >
> > > > Is there anything important missing which should go into the next
> > > > release? Otherwise I think we should also aim for more frequent
> > > > released and just make one again early next year, with all the
> > stuff
> > > we
> > > > might miss out now.
> > > >
> > > > We took in a patch - as part of OPENNLP-830 - to replace our
> > > self-made
> > > > hash table with the java.util.HashMap. This change is not
> backward
> > > > compatible for folks who extend AbstractModel.
> > > >
> > > > Should we go with 1.6.1 as a next version or should we make 1.7.0
> > to
> > > > reflect that?
> > > >
> > > > Previously we only had backward incompatible changes in versions
> > > which
> > > > bumped by the second number. Maybe that is better choice. It will
> > > > probably break some peoples code when they update.
> > > >
> > > > We also have lots of deprecated API still in OpenNLP, should we
> try
> > > to
> > > > remove as much as possible of it now?
> > > >
> > > > Jörn
> > > >
> > > >
> > >
> >
>
Re: Next release
Posted by Joern Kottmann <ko...@gmail.com>.
I suggest we remove more deprecated code, there is still a lot which could
be removed and is really old.
It is a bit of a boring task, if anyone has some spare cycles help would be
welcome.
Jörn
On Tue, Nov 8, 2016 at 9:59 AM, Aliaksandr Autayeu <al...@autayeu.com>
wrote:
> +1 for 1.7 (also due to lemmatized changes and removal of deprecated code).
>
> On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org> wrote:
>
> > Hello,
> >
> > +1 1.7.0 in next release and +1 for a yearly release
> >
> > Just to provide some info, the main changes in the lemmatizer have been:
> >
> > 1. Added a supervised statistical lemmatizer, usable from the CLI and
> > API. The supervised lemmaitzer now provides a much better coverage for
> > unknown words with respect to the previously existing dictionary-based
> > one.
> > 2. The lemmatizer component has been rewritten and the API therefore
> > has substantially changed. Thus, the changes in the Dictionary-based
> > lemmatizer are not backward compatible. In any case, I do not think
> > that so many people was using it and the change at using the API is
> > minor.
> >
> > The new statistical lemmatizer can support the Dictionary-based
> > lemmatizers often used to provide features for components such as Word
> > Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> > regard, it will be nice to aim at working on the development of those
> > two components for their release. Maybe the next release is too close,
> > but definitely for the next one.
> >
> > Cheers,
> >
> > Rodrigo
> >
> > On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> > <dr...@mail.nih.gov> wrote:
> > > Also the lemmatizer has significantly changed. I vote 1.7
> > >
> > > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> > >
> > > Hello all,
> > >
> > > since our last release it has been a while and we received quite a
> > few
> > > changes which would be nice to get released.
> > >
> > > There are still some open Jira issues, but mostly smaller things
> that
> > > can be wrapped up rather quickly.
> > >
> > > Is there anything important missing which should go into the next
> > > release? Otherwise I think we should also aim for more frequent
> > > released and just make one again early next year, with all the
> stuff
> > we
> > > might miss out now.
> > >
> > > We took in a patch - as part of OPENNLP-830 - to replace our
> > self-made
> > > hash table with the java.util.HashMap. This change is not backward
> > > compatible for folks who extend AbstractModel.
> > >
> > > Should we go with 1.6.1 as a next version or should we make 1.7.0
> to
> > > reflect that?
> > >
> > > Previously we only had backward incompatible changes in versions
> > which
> > > bumped by the second number. Maybe that is better choice. It will
> > > probably break some peoples code when they update.
> > >
> > > We also have lots of deprecated API still in OpenNLP, should we try
> > to
> > > remove as much as possible of it now?
> > >
> > > Jörn
> > >
> > >
> >
>
Re: Next release
Posted by Aliaksandr Autayeu <al...@autayeu.com>.
+1 for 1.7 (also due to lemmatized changes and removal of deprecated code).
On 8 November 2016 at 09:48, Rodrigo Agerri <ra...@apache.org> wrote:
> Hello,
>
> +1 1.7.0 in next release and +1 for a yearly release
>
> Just to provide some info, the main changes in the lemmatizer have been:
>
> 1. Added a supervised statistical lemmatizer, usable from the CLI and
> API. The supervised lemmaitzer now provides a much better coverage for
> unknown words with respect to the previously existing dictionary-based
> one.
> 2. The lemmatizer component has been rewritten and the API therefore
> has substantially changed. Thus, the changes in the Dictionary-based
> lemmatizer are not backward compatible. In any case, I do not think
> that so many people was using it and the change at using the API is
> minor.
>
> The new statistical lemmatizer can support the Dictionary-based
> lemmatizers often used to provide features for components such as Word
> Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> regard, it will be nice to aim at working on the development of those
> two components for their release. Maybe the next release is too close,
> but definitely for the next one.
>
> Cheers,
>
> Rodrigo
>
> On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> <dr...@mail.nih.gov> wrote:
> > Also the lemmatizer has significantly changed. I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> >
> > Hello all,
> >
> > since our last release it has been a while and we received quite a
> few
> > changes which would be nice to get released.
> >
> > There are still some open Jira issues, but mostly smaller things that
> > can be wrapped up rather quickly.
> >
> > Is there anything important missing which should go into the next
> > release? Otherwise I think we should also aim for more frequent
> > released and just make one again early next year, with all the stuff
> we
> > might miss out now.
> >
> > We took in a patch - as part of OPENNLP-830 - to replace our
> self-made
> > hash table with the java.util.HashMap. This change is not backward
> > compatible for folks who extend AbstractModel.
> >
> > Should we go with 1.6.1 as a next version or should we make 1.7.0 to
> > reflect that?
> >
> > Previously we only had backward incompatible changes in versions
> which
> > bumped by the second number. Maybe that is better choice. It will
> > probably break some peoples code when they update.
> >
> > We also have lots of deprecated API still in OpenNLP, should we try
> to
> > remove as much as possible of it now?
> >
> > Jörn
> >
> >
>
Re: Next release
Posted by Rodrigo Agerri <ra...@apache.org>.
Hello Chris,
Great! I was following the SentimentAnalyzer development and that will
be very nice.
Cheers,
R
On Tue, Nov 8, 2016 at 3:54 PM, Mattmann, Chris A (3010)
<ch...@jpl.nasa.gov> wrote:
> Hi Rodrigo I have a SentimentAnalyzer including the test code and one for Author
> and Age extraction. One was part of GSOC 2016 this past summer and the other
> was part of the DARPA MEMEX project. I’ll get them packaged up. Sorry have had
> low cycles available but will get them ready.
>
> Cheers,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Principal Data Scientist, Engineering Administrative Office (3010)
> Manager, Open Source Projects Formulation and Development Office (8212)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 180-503E, Mailstop: 180-502
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> On 11/8/16, 12:48 AM, "Rodrigo Agerri" <ra...@apache.org> wrote:
>
> Hello,
>
> +1 1.7.0 in next release and +1 for a yearly release
>
> Just to provide some info, the main changes in the lemmatizer have been:
>
> 1. Added a supervised statistical lemmatizer, usable from the CLI and
> API. The supervised lemmaitzer now provides a much better coverage for
> unknown words with respect to the previously existing dictionary-based
> one.
> 2. The lemmatizer component has been rewritten and the API therefore
> has substantially changed. Thus, the changes in the Dictionary-based
> lemmatizer are not backward compatible. In any case, I do not think
> that so many people was using it and the change at using the API is
> minor.
>
> The new statistical lemmatizer can support the Dictionary-based
> lemmatizers often used to provide features for components such as Word
> Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> regard, it will be nice to aim at working on the development of those
> two components for their release. Maybe the next release is too close,
> but definitely for the next one.
>
> Cheers,
>
> Rodrigo
>
> On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> <dr...@mail.nih.gov> wrote:
> > Also the lemmatizer has significantly changed. I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> >
> > Hello all,
> >
> > since our last release it has been a while and we received quite a few
> > changes which would be nice to get released.
> >
> > There are still some open Jira issues, but mostly smaller things that
> > can be wrapped up rather quickly.
> >
> > Is there anything important missing which should go into the next
> > release? Otherwise I think we should also aim for more frequent
> > released and just make one again early next year, with all the stuff we
> > might miss out now.
> >
> > We took in a patch - as part of OPENNLP-830 - to replace our self-made
> > hash table with the java.util.HashMap. This change is not backward
> > compatible for folks who extend AbstractModel.
> >
> > Should we go with 1.6.1 as a next version or should we make 1.7.0 to
> > reflect that?
> >
> > Previously we only had backward incompatible changes in versions which
> > bumped by the second number. Maybe that is better choice. It will
> > probably break some peoples code when they update.
> >
> > We also have lots of deprecated API still in OpenNLP, should we try to
> > remove as much as possible of it now?
> >
> > Jörn
> >
> >
>
>
Re: Next release
Posted by "Mattmann, Chris A (3010)" <ch...@jpl.nasa.gov>.
Hi Rodrigo I have a SentimentAnalyzer including the test code and one for Author
and Age extraction. One was part of GSOC 2016 this past summer and the other
was part of the DARPA MEMEX project. I’ll get them packaged up. Sorry have had
low cycles available but will get them ready.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010)
Manager, Open Source Projects Formulation and Development Office (8212)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 180-503E, Mailstop: 180-502
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On 11/8/16, 12:48 AM, "Rodrigo Agerri" <ra...@apache.org> wrote:
Hello,
+1 1.7.0 in next release and +1 for a yearly release
Just to provide some info, the main changes in the lemmatizer have been:
1. Added a supervised statistical lemmatizer, usable from the CLI and
API. The supervised lemmaitzer now provides a much better coverage for
unknown words with respect to the previously existing dictionary-based
one.
2. The lemmatizer component has been rewritten and the API therefore
has substantially changed. Thus, the changes in the Dictionary-based
lemmatizer are not backward compatible. In any case, I do not think
that so many people was using it and the change at using the API is
minor.
The new statistical lemmatizer can support the Dictionary-based
lemmatizers often used to provide features for components such as Word
Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
regard, it will be nice to aim at working on the development of those
two components for their release. Maybe the next release is too close,
but definitely for the next one.
Cheers,
Rodrigo
On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
<dr...@mail.nih.gov> wrote:
> Also the lemmatizer has significantly changed. I vote 1.7
>
> On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
>
> Hello all,
>
> since our last release it has been a while and we received quite a few
> changes which would be nice to get released.
>
> There are still some open Jira issues, but mostly smaller things that
> can be wrapped up rather quickly.
>
> Is there anything important missing which should go into the next
> release? Otherwise I think we should also aim for more frequent
> released and just make one again early next year, with all the stuff we
> might miss out now.
>
> We took in a patch - as part of OPENNLP-830 - to replace our self-made
> hash table with the java.util.HashMap. This change is not backward
> compatible for folks who extend AbstractModel.
>
> Should we go with 1.6.1 as a next version or should we make 1.7.0 to
> reflect that?
>
> Previously we only had backward incompatible changes in versions which
> bumped by the second number. Maybe that is better choice. It will
> probably break some peoples code when they update.
>
> We also have lots of deprecated API still in OpenNLP, should we try to
> remove as much as possible of it now?
>
> Jörn
>
>
Re: Next release
Posted by Joern Kottmann <ko...@gmail.com>.
Hmm, I think it is probably easier if we keep the master branch for the
release and have separate topic branches for new work and if necessary a
next branch. After the release is done we can merge the finished work into
master and repeat. That way we could have master always in a good state
which is almost ready for release.
Having a stable master which goes from release to release makes it also
easier to use git bisect to automatically find commits that broke something.
For some bigger changes I will also run more often the extended tests I
have, if i have those in a topic branch before we merge that would be
great, if there are issues we don't have to break the master branch. With
git it is easier to deal with branches than it was before with subversion.
My goal is to get this kind of workflow automated with a build server
running and reporting to us on each Pull Request.
Jörn
On Wed, Nov 9, 2016 at 9:52 AM, Rodrigo Agerri <ra...@apache.org> wrote:
> Hello,
>
> No problem. Should I just create a release-1.7 branch and so we can do
> all the work towards the next release there? Or would you prefer
> different branches?
>
> Cheers,
>
> R
>
> On Tue, Nov 8, 2016 at 12:07 PM, Joern Kottmann <ko...@gmail.com>
> wrote:
> > Hello Rodrigo,
> >
> > would you mind to add this to our README file?
> >
> > It is in opennlp-distr and should contain the notable changes for the
> > release, anyone else please also add in your changes there. Currently it
> > still contains the contents for 1.6.0.
> >
> > You can just start working on it in a separate branch, with git we can
> > support a work flow where we merge in features/changes when they are
> ready.
> > I thin this is also a really good approach because we can then run the
> > extensive tests before we merge a branch.
> >
> > Jörn
> >
> > On Tue, Nov 8, 2016 at 9:48 AM, Rodrigo Agerri <ra...@apache.org>
> wrote:
> >
> >> Hello,
> >>
> >> +1 1.7.0 in next release and +1 for a yearly release
> >>
> >> Just to provide some info, the main changes in the lemmatizer have been:
> >>
> >> 1. Added a supervised statistical lemmatizer, usable from the CLI and
> >> API. The supervised lemmaitzer now provides a much better coverage for
> >> unknown words with respect to the previously existing dictionary-based
> >> one.
> >> 2. The lemmatizer component has been rewritten and the API therefore
> >> has substantially changed. Thus, the changes in the Dictionary-based
> >> lemmatizer are not backward compatible. In any case, I do not think
> >> that so many people was using it and the change at using the API is
> >> minor.
> >>
> >> The new statistical lemmatizer can support the Dictionary-based
> >> lemmatizers often used to provide features for components such as Word
> >> Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> >> regard, it will be nice to aim at working on the development of those
> >> two components for their release. Maybe the next release is too close,
> >> but definitely for the next one.
> >>
> >> Cheers,
> >>
> >> Rodrigo
> >>
> >> On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> >> <dr...@mail.nih.gov> wrote:
> >> > Also the lemmatizer has significantly changed. I vote 1.7
> >> >
> >> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> >> >
> >> > Hello all,
> >> >
> >> > since our last release it has been a while and we received quite a
> >> few
> >> > changes which would be nice to get released.
> >> >
> >> > There are still some open Jira issues, but mostly smaller things
> that
> >> > can be wrapped up rather quickly.
> >> >
> >> > Is there anything important missing which should go into the next
> >> > release? Otherwise I think we should also aim for more frequent
> >> > released and just make one again early next year, with all the
> stuff
> >> we
> >> > might miss out now.
> >> >
> >> > We took in a patch - as part of OPENNLP-830 - to replace our
> >> self-made
> >> > hash table with the java.util.HashMap. This change is not backward
> >> > compatible for folks who extend AbstractModel.
> >> >
> >> > Should we go with 1.6.1 as a next version or should we make 1.7.0
> to
> >> > reflect that?
> >> >
> >> > Previously we only had backward incompatible changes in versions
> >> which
> >> > bumped by the second number. Maybe that is better choice. It will
> >> > probably break some peoples code when they update.
> >> >
> >> > We also have lots of deprecated API still in OpenNLP, should we
> try
> >> to
> >> > remove as much as possible of it now?
> >> >
> >> > Jörn
> >> >
> >> >
> >>
>
Re: Next release
Posted by Rodrigo Agerri <ra...@apache.org>.
Hello,
No problem. Should I just create a release-1.7 branch and so we can do
all the work towards the next release there? Or would you prefer
different branches?
Cheers,
R
On Tue, Nov 8, 2016 at 12:07 PM, Joern Kottmann <ko...@gmail.com> wrote:
> Hello Rodrigo,
>
> would you mind to add this to our README file?
>
> It is in opennlp-distr and should contain the notable changes for the
> release, anyone else please also add in your changes there. Currently it
> still contains the contents for 1.6.0.
>
> You can just start working on it in a separate branch, with git we can
> support a work flow where we merge in features/changes when they are ready.
> I thin this is also a really good approach because we can then run the
> extensive tests before we merge a branch.
>
> Jörn
>
> On Tue, Nov 8, 2016 at 9:48 AM, Rodrigo Agerri <ra...@apache.org> wrote:
>
>> Hello,
>>
>> +1 1.7.0 in next release and +1 for a yearly release
>>
>> Just to provide some info, the main changes in the lemmatizer have been:
>>
>> 1. Added a supervised statistical lemmatizer, usable from the CLI and
>> API. The supervised lemmaitzer now provides a much better coverage for
>> unknown words with respect to the previously existing dictionary-based
>> one.
>> 2. The lemmatizer component has been rewritten and the API therefore
>> has substantially changed. Thus, the changes in the Dictionary-based
>> lemmatizer are not backward compatible. In any case, I do not think
>> that so many people was using it and the change at using the API is
>> minor.
>>
>> The new statistical lemmatizer can support the Dictionary-based
>> lemmatizers often used to provide features for components such as Word
>> Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
>> regard, it will be nice to aim at working on the development of those
>> two components for their release. Maybe the next release is too close,
>> but definitely for the next one.
>>
>> Cheers,
>>
>> Rodrigo
>>
>> On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
>> <dr...@mail.nih.gov> wrote:
>> > Also the lemmatizer has significantly changed. I vote 1.7
>> >
>> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
>> >
>> > Hello all,
>> >
>> > since our last release it has been a while and we received quite a
>> few
>> > changes which would be nice to get released.
>> >
>> > There are still some open Jira issues, but mostly smaller things that
>> > can be wrapped up rather quickly.
>> >
>> > Is there anything important missing which should go into the next
>> > release? Otherwise I think we should also aim for more frequent
>> > released and just make one again early next year, with all the stuff
>> we
>> > might miss out now.
>> >
>> > We took in a patch - as part of OPENNLP-830 - to replace our
>> self-made
>> > hash table with the java.util.HashMap. This change is not backward
>> > compatible for folks who extend AbstractModel.
>> >
>> > Should we go with 1.6.1 as a next version or should we make 1.7.0 to
>> > reflect that?
>> >
>> > Previously we only had backward incompatible changes in versions
>> which
>> > bumped by the second number. Maybe that is better choice. It will
>> > probably break some peoples code when they update.
>> >
>> > We also have lots of deprecated API still in OpenNLP, should we try
>> to
>> > remove as much as possible of it now?
>> >
>> > Jörn
>> >
>> >
>>
Re: Next release
Posted by Joern Kottmann <ko...@gmail.com>.
Hello Rodrigo,
would you mind to add this to our README file?
It is in opennlp-distr and should contain the notable changes for the
release, anyone else please also add in your changes there. Currently it
still contains the contents for 1.6.0.
You can just start working on it in a separate branch, with git we can
support a work flow where we merge in features/changes when they are ready.
I thin this is also a really good approach because we can then run the
extensive tests before we merge a branch.
Jörn
On Tue, Nov 8, 2016 at 9:48 AM, Rodrigo Agerri <ra...@apache.org> wrote:
> Hello,
>
> +1 1.7.0 in next release and +1 for a yearly release
>
> Just to provide some info, the main changes in the lemmatizer have been:
>
> 1. Added a supervised statistical lemmatizer, usable from the CLI and
> API. The supervised lemmaitzer now provides a much better coverage for
> unknown words with respect to the previously existing dictionary-based
> one.
> 2. The lemmatizer component has been rewritten and the API therefore
> has substantially changed. Thus, the changes in the Dictionary-based
> lemmatizer are not backward compatible. In any case, I do not think
> that so many people was using it and the change at using the API is
> minor.
>
> The new statistical lemmatizer can support the Dictionary-based
> lemmatizers often used to provide features for components such as Word
> Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
> regard, it will be nice to aim at working on the development of those
> two components for their release. Maybe the next release is too close,
> but definitely for the next one.
>
> Cheers,
>
> Rodrigo
>
> On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
> <dr...@mail.nih.gov> wrote:
> > Also the lemmatizer has significantly changed. I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
> >
> > Hello all,
> >
> > since our last release it has been a while and we received quite a
> few
> > changes which would be nice to get released.
> >
> > There are still some open Jira issues, but mostly smaller things that
> > can be wrapped up rather quickly.
> >
> > Is there anything important missing which should go into the next
> > release? Otherwise I think we should also aim for more frequent
> > released and just make one again early next year, with all the stuff
> we
> > might miss out now.
> >
> > We took in a patch - as part of OPENNLP-830 - to replace our
> self-made
> > hash table with the java.util.HashMap. This change is not backward
> > compatible for folks who extend AbstractModel.
> >
> > Should we go with 1.6.1 as a next version or should we make 1.7.0 to
> > reflect that?
> >
> > Previously we only had backward incompatible changes in versions
> which
> > bumped by the second number. Maybe that is better choice. It will
> > probably break some peoples code when they update.
> >
> > We also have lots of deprecated API still in OpenNLP, should we try
> to
> > remove as much as possible of it now?
> >
> > Jörn
> >
> >
>
Re: Next release
Posted by Rodrigo Agerri <ra...@apache.org>.
Hello,
+1 1.7.0 in next release and +1 for a yearly release
Just to provide some info, the main changes in the lemmatizer have been:
1. Added a supervised statistical lemmatizer, usable from the CLI and
API. The supervised lemmaitzer now provides a much better coverage for
unknown words with respect to the previously existing dictionary-based
one.
2. The lemmatizer component has been rewritten and the API therefore
has substantially changed. Thus, the changes in the Dictionary-based
lemmatizer are not backward compatible. In any case, I do not think
that so many people was using it and the change at using the API is
minor.
The new statistical lemmatizer can support the Dictionary-based
lemmatizers often used to provide features for components such as Word
Sense Disambiguation, Opinion Mining/Sentiment Analysis, etc. In this
regard, it will be nice to aim at working on the development of those
two components for their release. Maybe the next release is too close,
but definitely for the next one.
Cheers,
Rodrigo
On Mon, Nov 7, 2016 at 7:01 PM, Russ, Daniel (NIH/CIT) [E]
<dr...@mail.nih.gov> wrote:
> Also the lemmatizer has significantly changed. I vote 1.7
>
> On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
>
> Hello all,
>
> since our last release it has been a while and we received quite a few
> changes which would be nice to get released.
>
> There are still some open Jira issues, but mostly smaller things that
> can be wrapped up rather quickly.
>
> Is there anything important missing which should go into the next
> release? Otherwise I think we should also aim for more frequent
> released and just make one again early next year, with all the stuff we
> might miss out now.
>
> We took in a patch - as part of OPENNLP-830 - to replace our self-made
> hash table with the java.util.HashMap. This change is not backward
> compatible for folks who extend AbstractModel.
>
> Should we go with 1.6.1 as a next version or should we make 1.7.0 to
> reflect that?
>
> Previously we only had backward incompatible changes in versions which
> bumped by the second number. Maybe that is better choice. It will
> probably break some peoples code when they update.
>
> We also have lots of deprecated API still in OpenNLP, should we try to
> remove as much as possible of it now?
>
> Jörn
>
>
Re: Next release
Posted by "Russ, Daniel (NIH/CIT) [E]" <dr...@mail.nih.gov>.
Also the lemmatizer has significantly changed. I vote 1.7
On 11/7/16, 12:59 PM, "Joern Kottmann" <ko...@gmail.com> wrote:
Hello all,
since our last release it has been a while and we received quite a few
changes which would be nice to get released.
There are still some open Jira issues, but mostly smaller things that
can be wrapped up rather quickly.
Is there anything important missing which should go into the next
release? Otherwise I think we should also aim for more frequent
released and just make one again early next year, with all the stuff we
might miss out now.
We took in a patch - as part of OPENNLP-830 - to replace our self-made
hash table with the java.util.HashMap. This change is not backward
compatible for folks who extend AbstractModel.
Should we go with 1.6.1 as a next version or should we make 1.7.0 to
reflect that?
Previously we only had backward incompatible changes in versions which
bumped by the second number. Maybe that is better choice. It will
probably break some peoples code when they update.
We also have lots of deprecated API still in OpenNLP, should we try to
remove as much as possible of it now?
Jörn