Preparing for the next release

[Joern Kottmann]

Hello all,

please don't commit any new changes (code freeze) because we are now
preparing for the 1.8.3 release.

BR,
Jörn

Re: Next release

[Tommaso Teofili]

I would like to have OPENNLP-890 in for 1.7.1, I can work on it in a couple
of weeks.

Other than that I second more frequent releases, depending on dev pace
perhaps we could plan for a release every X months (3 sounds best to me,
but probably 6 is more adeguate for our dev effort).

Regards,
Tommaso

Il giorno dom 1 gen 2017 alle ore 20:13 Joern Kottmann 
ha scritto:

> Hello all,
>
> now all the tests we do to release OpenNLP are automated and that
> allows us to also do more frequent releases.
>
> I would like to do a couple of releases this year and not just one,
> so the next one will probably be 1.7.1 and we should do it rather soon.
>
> There is a PR we can merge for it, and I will also have time to work on
> a couple of jira issues.
>
> If you have something you would like to get in please start working on
> it now and get the changes merged into trunk.
>
> Any opinions?
>
> Jörn
>

Next release

[Joern Kottmann]

Hello all,

now all the tests we do to release OpenNLP are automated and that
allows us to also do more frequent releases.

I would like to do a couple of releases this year and not just one,
so the next one will probably be 1.7.1 and we should do it rather soon.

There is a PR we can merge for it, and I will also have time to work on
a couple of jira issues.

If you have something you would like to get in please start working on
it now and get the changes merged into trunk.

Any opinions?

Jörn

Re: Next release

[Cohan Sujay Carlos]

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:


  org.apache.opennlp
  opennlp-tools
  *1.6.1-SNAPSHOT*


Cohan Sujay Carlos
Aiaioo Labs, +91-77605-80015, http://www.aiaioo.com

On Wed, Nov 23, 2016 at 5:36 PM, Rodrigo Agerri  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 
> 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 :
> >
> >> 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  >
> >> 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 :
> >> >
> >> > > 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 <
> >> > aliaksa...@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 
> >> > 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
> >> > &

Re: Next release

[Rodrigo Agerri]

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  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 :
>
>> 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 
>> 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 :
>> >
>> > > 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 <
>> > aliaksa...@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 
>> > 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]
>> > > > >  wrote:
>> > > > > > Also the lemmatizer has significantly changed.  I vote 1.7
>> > > > > >
>> > > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" 
>> 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

[William Colen]

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 :

> 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 
> 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 :
> >
> > > 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 <
> > aliaksa...@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 
> > 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]
> > > > >  wrote:
> > > > > > Also the lemmatizer has significantly changed.  I vote 1.7
> > > > > >
> > > > > > On 11/7/16, 12:59 PM, "Joern Kottmann" 
> 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

[Joern Kottmann]

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 
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 :
>
> > 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 <
> aliaksa...@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 
> 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]
> > > >  wrote:
> > > > > Also the lemmatizer has significantly changed.  I vote 1.7
> > > > >
> > > > > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[William Colen]

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 :

> 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  >
> wrote:
>
> > +1 for 1.7 (also due to lemmatized changes and removal of deprecated
> code).
> >
> > On 8 November 2016 at 09:48, Rodrigo Agerri  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]
> > >  wrote:
> > > > Also the lemmatizer has significantly changed.  I vote 1.7
> > > >
> > > > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Joern Kottmann]

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  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 
> 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 
> 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]
> >>  wrote:
> >> > Also the lemmatizer has significantly changed.  I vote 1.7
> >> >
> >> > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Rodrigo Agerri]

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)
 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.mattm...@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"  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]
>  wrote:
> > Also the lemmatizer has significantly changed.  I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Rodrigo Agerri]

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  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  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]
>>  wrote:
>> > Also the lemmatizer has significantly changed.  I vote 1.7
>> >
>> > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Mattmann, Chris A (3010)]

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.mattm...@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"  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]
 wrote:
> Also the lemmatizer has significantly changed.  I vote 1.7
>
> On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Joern Kottmann]

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 
wrote:

> +1 for 1.7 (also due to lemmatized changes and removal of deprecated code).
>
> On 8 November 2016 at 09:48, Rodrigo Agerri  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]
> >  wrote:
> > > Also the lemmatizer has significantly changed.  I vote 1.7
> > >
> > > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Joern Kottmann]

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  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]
>  wrote:
> > Also the lemmatizer has significantly changed.  I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Aliaksandr Autayeu]

+1 for 1.7 (also due to lemmatized changes and removal of deprecated code).

On 8 November 2016 at 09:48, Rodrigo Agerri  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]
>  wrote:
> > Also the lemmatizer has significantly changed.  I vote 1.7
> >
> > On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Rodrigo Agerri]

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]
 wrote:
> Also the lemmatizer has significantly changed.  I vote 1.7
>
> On 11/7/16, 12:59 PM, "Joern Kottmann"  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

[Tommaso Teofili]

+1 for 1.7
Il giorno lun 7 nov 2016 alle 19:27 William Colen 
ha scritto:

> +1 for 1.7
>
> William
>
> 2016-11-07 16:22 GMT-02:00 Joern Kottmann :
>
> > I am also in favor of 1.7.
> >
> > Jörn
> >
> > On Mon, 2016-11-07 at 18:01 +, 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"  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

[William Colen]

+1 for 1.7

William

2016-11-07 16:22 GMT-02:00 Joern Kottmann :

> I am also in favor of 1.7.
>
> Jörn
>
> On Mon, 2016-11-07 at 18:01 +, 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"  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

[Joern Kottmann]

I am also in favor of 1.7.

Jörn

On Mon, 2016-11-07 at 18:01 +, 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"  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

[Mattmann, Chris A (3010)]

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.mattm...@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"  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

[Russ, Daniel (NIH/CIT) [E]]

Also the lemmatizer has significantly changed.  I vote 1.7

On 11/7/16, 12:59 PM, "Joern Kottmann"  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

Next release

[Joern Kottmann]

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

[Rodrigo Agerri]

+1 for William as RM

R

On Mon, Nov 24, 2014 at 3:18 PM, Jörn Kottmann  wrote:
> On 11/21/2014 01:26 PM, William Colen wrote:
>>
>> +1 to start the release process
>>
>> I candidate myself as release manager for the 1.6.0.
>>
>
>
> +1 for William as RM
>
> Jörn

Re: Next release

[Jörn Kottmann]

On 11/21/2014 01:26 PM, William Colen wrote:

+1 to start the release process

I candidate myself as release manager for the 1.6.0.




+1 for William as RM

Jörn

Re: Next release (was: Re: 1.6.0 maven repo)

[William Colen]

+1 to start the release process

I candidate myself as release manager for the 1.6.0.

2014-11-20 18:32 GMT-02:00 Vinh Khuc :

> +1 for the release of 1.6.0 RC
>
> Vinh
>
> On Thu, Nov 20, 2014 at 3:24 PM, Joern Kottmann 
> wrote:
>
> > Yes, all the important issues, expect one (OPENNLP-730) are closed now.
> > There are still a couple of issues open about name finder feature
> > generators, but those could also be added to OpenNLP in a 1.6.1 release
> > or during testing.
> >
> > +1 to make the first RC for 1.6.0 and start testing it
> >
> > Jörn
> >
> > On Thu, 2014-11-20 at 07:33 +, Rodrigo Agerri wrote:
> > > +1 to start making a release. I would like to be involved too.
> > >
> > > R
> > > On 19 Nov 2014 23:40, "Joern Kottmann"  wrote:
> > >
> > > > Hello,
> > > >
> > > > yes, that should be the current state.
> > > >
> > > > Can you please elaborate on the issue you have.
> > > > Do you get an old version?
> > > >
> > > > We should try to make a release of 1.6.0, I think most issues
> > > > are already solved and remaining bugs we will uncover during the
> manual
> > > > testing phase.
> > > >
> > > > Jörn
> > > >
> > > > On Wed, 2014-11-19 at 21:20 +0100, Rodrigo Agerri wrote:
> > > > > Hi
> > > > >
> > > > > Any chance to release snapshot repos to maven central? Or to an
> > apache
> > > > > snapshots repo?
> > > > >
> > > > > It would make the use of current trunk via API much easier.
> > > > >
> > > > > Cheers
> > > > >
> > > > > Rodrigo
> > > >
> > > >
> > > >
> >
> >
> >
>
>
> --
> Vinh Khuc
>

Re: Next release (was: Re: 1.6.0 maven repo)

[Vinh Khuc]

+1 for the release of 1.6.0 RC

Vinh

On Thu, Nov 20, 2014 at 3:24 PM, Joern Kottmann  wrote:

> Yes, all the important issues, expect one (OPENNLP-730) are closed now.
> There are still a couple of issues open about name finder feature
> generators, but those could also be added to OpenNLP in a 1.6.1 release
> or during testing.
>
> +1 to make the first RC for 1.6.0 and start testing it
>
> Jörn
>
> On Thu, 2014-11-20 at 07:33 +, Rodrigo Agerri wrote:
> > +1 to start making a release. I would like to be involved too.
> >
> > R
> > On 19 Nov 2014 23:40, "Joern Kottmann"  wrote:
> >
> > > Hello,
> > >
> > > yes, that should be the current state.
> > >
> > > Can you please elaborate on the issue you have.
> > > Do you get an old version?
> > >
> > > We should try to make a release of 1.6.0, I think most issues
> > > are already solved and remaining bugs we will uncover during the manual
> > > testing phase.
> > >
> > > Jörn
> > >
> > > On Wed, 2014-11-19 at 21:20 +0100, Rodrigo Agerri wrote:
> > > > Hi
> > > >
> > > > Any chance to release snapshot repos to maven central? Or to an
> apache
> > > > snapshots repo?
> > > >
> > > > It would make the use of current trunk via API much easier.
> > > >
> > > > Cheers
> > > >
> > > > Rodrigo
> > >
> > >
> > >
>
>
>


-- 
Vinh Khuc

Next release (was: Re: 1.6.0 maven repo)

[Joern Kottmann]

Yes, all the important issues, expect one (OPENNLP-730) are closed now.
There are still a couple of issues open about name finder feature
generators, but those could also be added to OpenNLP in a 1.6.1 release
or during testing.

+1 to make the first RC for 1.6.0 and start testing it

Jörn

On Thu, 2014-11-20 at 07:33 +, Rodrigo Agerri wrote:
> +1 to start making a release. I would like to be involved too.
> 
> R
> On 19 Nov 2014 23:40, "Joern Kottmann"  wrote:
> 
> > Hello,
> >
> > yes, that should be the current state.
> >
> > Can you please elaborate on the issue you have.
> > Do you get an old version?
> >
> > We should try to make a release of 1.6.0, I think most issues
> > are already solved and remaining bugs we will uncover during the manual
> > testing phase.
> >
> > Jörn
> >
> > On Wed, 2014-11-19 at 21:20 +0100, Rodrigo Agerri wrote:
> > > Hi
> > >
> > > Any chance to release snapshot repos to maven central? Or to an apache
> > > snapshots repo?
> > >
> > > It would make the use of current trunk via API much easier.
> > >
> > > Cheers
> > >
> > > Rodrigo
> >
> >
> >

Re: Next release

[Benson Margulies]

yes, ossrh will do that

On Feb 19, 2013, at 8:38 AM, William Colen  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 
> wrote:
>
>> upload to central via ossrh.
>>
>> On Feb 18, 2013, at 12:46 PM, William Colen 
>> 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 
>> 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

[Jörn Kottmann]

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

[William Colen]

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 wrote:

> upload to central via ossrh.
>
> On Feb 18, 2013, at 12:46 PM, William Colen 
> 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 
> 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

[Jörn Kottmann]

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

[Aliaksandr Autayeu]

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

[Benson Margulies]

upload to central via ossrh.

On Feb 18, 2013, at 12:46 PM, William Colen  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  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
>>
>> Jörn
>>

Re: Next release

[William Colen]

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  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
>
> Jörn
>

Re: Next release

[Rodrigo Agerri]

On Mon, Feb 18, 2013 at 2:56 PM, Jörn Kottmann  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

[Jörn Kottmann]

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

[William Colen]

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  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
>>
>>
>> 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

[Jörn Kottmann]

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

[Jörn Kottmann]

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

[Rodrigo Agerri]

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  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  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?
>>
>>
>> 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

[Jörn Kottmann]

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

[William Colen]

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  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?
>
>
> 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

[Lance Norskog]

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

[Jörn Kottmann]

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.co...@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 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: kottm...@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

[Boris Galitsky]

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.co...@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 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: kottm...@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
> >
> >
  

pom.xml
Description: XML document

Re: Next release

[William Colen]

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 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: kottm...@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

[Aliaksandr Autayeu]

+1! Well said.

Aliaksandr

On Thu, Feb 14, 2013 at 1:31 PM, William Colen 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  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

[Jason Baldridge]

+1

On Thu, Feb 14, 2013 at 6:31 AM, William Colen 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  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

[Boris Galitsky]

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: kottm...@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

[Jörn Kottmann]

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

[William Colen]

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  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

[Jörn Kottmann]

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

[James Kosin]

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: Next release

[James Kosin]

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

[Jim - FooBar();]

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

[Jörn Kottmann]

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  
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

[Jim foo.bar]

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  
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

[Jörn Kottmann]

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  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

[Jörn Kottmann]

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

[William Colen]

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  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
>

Next release

[Jörn Kottmann]

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