[jira] [Commented] (NUTCH-2654) Remove obsolete index-writer configuration in conf/

2019-09-02 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/NUTCH-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920928#comment-16920928 ] ASF GitHub Bot commented on NUTCH-2654: --- r0ann3l commented on issue #468: NUTCH-2654: The obsolete

Re: [DISCUSS] Release 1.16?

2019-09-02 Thread Jorge Betancourt
Hi Seb! +1 From my side. As you said, a release is already in order. I will go over the issues/PRs on the repo as well. Best Regards, Jorge On Mon, Sep 2, 2019 at 5:05 PM Sebastian Nagel wrote: > Hi all, > > more than 90 issues are fixed now: >

[jira] [Commented] (NUTCH-2731) Solr Cleanup Step Fails when Authentication is Required

2019-09-02 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/NUTCH-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920920#comment-16920920 ] ASF GitHub Bot commented on NUTCH-2731: --- sebastian-nagel commented on issue #464: NUTCH-2731 Fix to

[jira] [Commented] (NUTCH-2654) Remove obsolete index-writer configuration in conf/

2019-09-02 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/NUTCH-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920849#comment-16920849 ] ASF GitHub Bot commented on NUTCH-2654: --- jorgelbg commented on issue #468: NUTCH-2654: The obsolete

[jira] [Commented] (NUTCH-2654) Remove obsolete index-writer configuration in conf/

2019-09-02 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/NUTCH-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920910#comment-16920910 ] ASF GitHub Bot commented on NUTCH-2654: --- sebastian-nagel commented on issue #468: NUTCH-2654: The

[DISCUSS] Release 1.16?

2019-09-02 Thread Sebastian Nagel
Hi all, more than 90 issues are fixed now: https://issues.apache.org/jira/projects/NUTCH/versions/12343430 The last release (1.15) is already more than one year ago (July 25, 2018). It's time! Of course, we'll check all remaining issues whether they should be fixed now or can be moved to be