1.7.2 release

[Joern Kottmann <jo...@apache.org>]

Dear all,

We will be making a 1.7.2 release of OpenNLP today. All issues in jira are
closed now.

Jörn

Re: 1.7.2 release

[Joern Kottmann <jo...@apache.org>]

I was not referring to the things you mentioned.

To ensure that OpenNLP works correctly all components have to be trained on
larger data sets and then evaluated against a larger amount of test data.
We often do changes where we expect the behavior of the component not to
change.

In the past those tests where all manual and often took weeks to be
finished, because they often showed signs of bugs which typically were hard
to track down.

Now we have a set of evaluation tests that can be run fully automatic. This
means also that the tests are run more frequently during development,
especially for high-risk changes, and we now should see problems before we
merge new work into master.

Jörn


On Wed, Feb 1, 2017 at 2:59 PM, Richard Eckart de Castilho <re...@apache.org>
wrote:

> On 01.02.2017, at 14:35, Joern Kottmann <jo...@apache.org> wrote:
> >
> > The project is now more agile and we can cut a release without a lot of
> > overhead. We spent years working toward that goal.
> > Now we will release a major version 1.x.0 every quarter and one or two
> > minor 1.x.y versions every month.
>
> What did you do to minimize the release overhead?
>
> When voting on a release, I find myself double-checking license files,
> changes in dependencies, checking signatures, etc. the most
> time-consuming part (like minimum 1-2 hours). Did you somehow automatize
> this (or maybe I'm just spending way too much time on details...).
>
> Cheers,
>
> -- Richard
>
>

Re: 1.7.2 release

[Richard Eckart de Castilho <re...@apache.org>]

On 01.02.2017, at 14:35, Joern Kottmann <jo...@apache.org> wrote:
> 
> The project is now more agile and we can cut a release without a lot of
> overhead. We spent years working toward that goal.
> Now we will release a major version 1.x.0 every quarter and one or two
> minor 1.x.y versions every month.

What did you do to minimize the release overhead?

When voting on a release, I find myself double-checking license files,
changes in dependencies, checking signatures, etc. the most
time-consuming part (like minimum 1-2 hours). Did you somehow automatize
this (or maybe I'm just spending way too much time on details...).

Cheers,

-- Richard 
 

Re: 1.7.2 release

[Joern Kottmann <jo...@apache.org>]

The project is now more agile and we can cut a release without a lot of
overhead. We spent years working toward that goal.
Now we will release a major version 1.x.0 every quarter and one or two
minor 1.x.y versions every month.

Jörn


On Wed, Feb 1, 2017 at 1:33 PM, Richard Eckart de Castilho <re...@apache.org>
wrote:

> Hi Jörn,
>
> I am curious - is there a specific reason that OpenNLP suddenly
> has this flurry of activity?
>
> Best,
>
> -- Richard
>
> > On 31.01.2017, at 13:45, Joern Kottmann <jo...@apache.org> wrote:
> >
> > Dear all,
> >
> > We will be making a 1.7.2 release of OpenNLP today. All issues in jira
> are
> > closed now.
> >
> > Jörn
>
>

Re: 1.7.2 release

[Richard Eckart de Castilho <re...@apache.org>]

Hi Jörn,

I am curious - is there a specific reason that OpenNLP suddenly
has this flurry of activity?

Best,

-- Richard

> On 31.01.2017, at 13:45, Joern Kottmann <jo...@apache.org> wrote:
> 
> Dear all,
> 
> We will be making a 1.7.2 release of OpenNLP today. All issues in jira are
> closed now.
> 
> Jörn