Re: OpenNLP 1.6.0 RC 4 ready for testing
Hello, I tested the pos tagger, namefinder and constituent parser in my projects and no problems reported. I am not aware of any issues left for next RC. Cheers, R On Fri, May 29, 2015 at 5:49 PM, Joern Kottmann kottm...@gmail.com wrote: I accidentally didn't include the dev list in my reply. Here are my two replies: Ok, that is great, then we don't need to do anything. I found a bug in the brat parser and fixed it already OPENNLP-784. Would be nice to get it in the release. Looks like we have to make one more RC to fix the notice and license file for the binary distribution. There was also a fix for the README. The test plan has some details about that. And just today I discovered a bug in the Name Finder, looks like it ignores the custom factory. We should get that fixed too before the next RC. I am currently trying to train a name finder with a custom factory for one of my work projects and in the process of doing that I started to debug that particular issue. I will open a jira issue for it. Anyone else please download RC 4 and give it a try with your projects. We are happy about every bug we can avoid shipping. And the second one: The name finder bug is now fixed. Should we go ahead and make the next RC? Are there any outstanding issues left which would prevent us from releasing it? I am not aware of any. Jörn On Thu, 2015-05-28 at 07:56 -0300, William Colen wrote: Yes, the sentence detector does not match, but it is such a small change that I would not even investigate. It is an empty line that used to be included in the 1.5.3 output, but it is not included in 1.6.0 anymore: Output in 1.5.3: Imagem inline 1 Output in 1.6.0: Imagem inline 3 I would ignore the change. Thank you, William 2015-05-28 7:28 GMT-03:00 Joern Kottmann kottm...@gmail.com: The chunker and parser tests are fine now. Do you know what's the deal with the sentence detector? The compatibility test is marked as failed. Can we leave it like that or do we have to fix some bugs? Jörn On May 23, 2015 5:35 AM, William Colen co...@apache.org wrote: Our fourth release candidate is ready for testing. RC 3 failed in the compatibility, regression and performance tests, which are fixed in RC 4. The RC 4 can be downloaded from here: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/ To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 The current test plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/TestPlan1.6.0 Please sign up for tasks in the test plan. The release plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/ReleasePlanAndTasks1.6.0 The release contains quite some changes, please refer to the contained issue list for details. For your convenience, a copy of the issue list, as well as the release notes and the readme, can be found in the following link: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/RELEASE_NOTES.html Thank you, William
Re: OpenNLP 1.6.0 RC 4 ready for testing
Btw. usually, there is little to no difference between the latest SNAPSHOT version, e.g. 1.6.0-SNAPSHOT in this case, and the RC. You could switch your CI to use the SNAPSHOT versions from the Apache repos. Please mind that these SNAPSHOTS are *not* releases, did not generally undergo the process necessary for a release, and are not meant for general consumption. Cheers, -- Richard On 01.06.2015, at 16:29, Richard Eckart de Castilho richard.eck...@gmail.com wrote: Hi, this is not a release - it is a release CANDIDATE. The procedure used here is the typical Apache procedure: - create release candidate - ask PMC members to check the RC and vote on it - if vote passes, the release is complete It is not possible to create a release without the votes. I think you are confusing a release candidate with a public beta release. Mind that a beta-release would also have to go through the process defined above. tl:dr: Do not test this on your CI machines or if you do, configure the respective builds to use a separate repository to avoid the problem you desribe. Cheers, -- Richard On 01.06.2015, at 16:21, František Hartman frant.ha...@gmail.com wrote: Hi, I wanted try the RC4 in our project. But this gives me headaches: To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 I don't understand why it is done this way, instead of releasing the RC under version 1.6.0-RC4. Consider this scenario - if I add this repository into my pom and use version 1.6.0, then the local maven repository of every developer on our project and every repository on our CI machines will get polluted with RC4 artifacts labelled as 1.6.0. When there is a final 1.6.0 release maven will not re-download them (it considers versions final and immutable unless labelled as SNAPSHOT). Somebody will have to go and manually delete these. Would it be possible to re-release with different version? F.
Re: OpenNLP 1.6.0 RC 4 ready for testing
Hi, this is not a release - it is a release CANDIDATE. The procedure used here is the typical Apache procedure: - create release candidate - ask PMC members to check the RC and vote on it - if vote passes, the release is complete It is not possible to create a release without the votes. I think you are confusing a release candidate with a public beta release. Mind that a beta-release would also have to go through the process defined above. tl:dr: Do not test this on your CI machines or if you do, configure the respective builds to use a separate repository to avoid the problem you desribe. Cheers, -- Richard On 01.06.2015, at 16:21, František Hartman frant.ha...@gmail.com wrote: Hi, I wanted try the RC4 in our project. But this gives me headaches: To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 I don't understand why it is done this way, instead of releasing the RC under version 1.6.0-RC4. Consider this scenario - if I add this repository into my pom and use version 1.6.0, then the local maven repository of every developer on our project and every repository on our CI machines will get polluted with RC4 artifacts labelled as 1.6.0. When there is a final 1.6.0 release maven will not re-download them (it considers versions final and immutable unless labelled as SNAPSHOT). Somebody will have to go and manually delete these. Would it be possible to re-release with different version? F.
Re: OpenNLP 1.6.0 RC 4 ready for testing
Hi, thanks for quick response. By release I meant upload release candidate into public maven repository, not actually releasing final version. Sorry for my misunderstanding the purpose of your release candidate. Generally in context of other open source projects (some Apache included) RC (or any other label like alpha, beta, milestone) = public beta. And they publish the artifacts properly labelled as such, some examples: http://search.maven.org/#artifactdetails%7Corg.apache.httpcomponents%7Chttpclient%7C4.4-alpha1%7Cjar http://repo.springsource.org/milestone/org/springframework/spring-core/4.2.0.RC1/ Would be great if opennlp did the same. Cheers, F. 2015-06-01 15:37 GMT+01:00 Richard Eckart de Castilho richard.eck...@gmail.com: Btw. usually, there is little to no difference between the latest SNAPSHOT version, e.g. 1.6.0-SNAPSHOT in this case, and the RC. You could switch your CI to use the SNAPSHOT versions from the Apache repos. Please mind that these SNAPSHOTS are *not* releases, did not generally undergo the process necessary for a release, and are not meant for general consumption. Cheers, -- Richard On 01.06.2015, at 16:29, Richard Eckart de Castilho richard.eck...@gmail.com wrote: Hi, this is not a release - it is a release CANDIDATE. The procedure used here is the typical Apache procedure: - create release candidate - ask PMC members to check the RC and vote on it - if vote passes, the release is complete It is not possible to create a release without the votes. I think you are confusing a release candidate with a public beta release. Mind that a beta-release would also have to go through the process defined above. tl:dr: Do not test this on your CI machines or if you do, configure the respective builds to use a separate repository to avoid the problem you desribe. Cheers, -- Richard On 01.06.2015, at 16:21, František Hartman frant.ha...@gmail.com wrote: Hi, I wanted try the RC4 in our project. But this gives me headaches: To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 I don't understand why it is done this way, instead of releasing the RC under version 1.6.0-RC4. Consider this scenario - if I add this repository into my pom and use version 1.6.0, then the local maven repository of every developer on our project and every repository on our CI machines will get polluted with RC4 artifacts labelled as 1.6.0. When there is a final 1.6.0 release maven will not re-download them (it considers versions final and immutable unless labelled as SNAPSHOT). Somebody will have to go and manually delete these. Would it be possible to re-release with different version? F.
Re: OpenNLP 1.6.0 RC 4 ready for testing
On 29.05.2015, at 17:49, Joern Kottmann kottm...@gmail.com wrote: Anyone else please download RC 4 and give it a try with your projects. We are happy about every bug we can avoid shipping. I locally and briefly tested DKPro Core against the OpenNLP RC 4 and hit no issues. Some API has changed compared to the last version, but nothing that could not be worked around easily. Cheers, -- Richard
Re: OpenNLP 1.6.0 RC 4 ready for testing
The chunker and parser tests are fine now. Do you know what's the deal with the sentence detector? The compatibility test is marked as failed. Can we leave it like that or do we have to fix some bugs? Jörn On May 23, 2015 5:35 AM, William Colen co...@apache.org wrote: Our fourth release candidate is ready for testing. RC 3 failed in the compatibility, regression and performance tests, which are fixed in RC 4. The RC 4 can be downloaded from here: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/ To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 The current test plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/TestPlan1.6.0 Please sign up for tasks in the test plan. The release plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/ReleasePlanAndTasks1.6.0 The release contains quite some changes, please refer to the contained issue list for details. For your convenience, a copy of the issue list, as well as the release notes and the readme, can be found in the following link: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/RELEASE_NOTES.html Thank you, William
Re: OpenNLP 1.6.0 RC 4 ready for testing
Yes, the sentence detector does not match, but it is such a small change that I would not even investigate. It is an empty line that used to be included in the 1.5.3 output, but it is not included in 1.6.0 anymore: *Output in 1.5.3:* [image: Imagem inline 1] *Output in 1.6.0:* [image: Imagem inline 3] I would ignore the change. Thank you, William 2015-05-28 7:28 GMT-03:00 Joern Kottmann kottm...@gmail.com: The chunker and parser tests are fine now. Do you know what's the deal with the sentence detector? The compatibility test is marked as failed. Can we leave it like that or do we have to fix some bugs? Jörn On May 23, 2015 5:35 AM, William Colen co...@apache.org wrote: Our fourth release candidate is ready for testing. RC 3 failed in the compatibility, regression and performance tests, which are fixed in RC 4. The RC 4 can be downloaded from here: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/ To use it in a maven build set the version for opennlp-tools or opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: https://repository.apache.org/content/repositories/orgapacheopennlp-1003 The current test plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/TestPlan1.6.0 Please sign up for tasks in the test plan. The release plan can be found here: https://cwiki.apache.org/confluence/display/OPENNLP/ReleasePlanAndTasks1.6.0 The release contains quite some changes, please refer to the contained issue list for details. For your convenience, a copy of the issue list, as well as the release notes and the readme, can be found in the following link: http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/RELEASE_NOTES.html Thank you, William
