Re: [VOTE] Approve the release of Apache Lucene.Net 2.0 build 003 incubating

2007-03-05 Thread Yonik Seeley
On 3/5/07, George Aroush <[EMAIL PROTECTED]> wrote: As for #3, I can use some more comment. The current header reflect what's found in the Java Lucene source code such that any place Java Lucene uses the newer header (http://www.apache.org/legal/src-headers.html#headers) so is Apache Lucene.Net.

RE: [VOTE] Approve the release of Apache Lucene.Net 2.0 build 003 incubating

2007-03-05 Thread George Aroush
Hi Dan and all, Many thanks to everyone who took the time to review this release and comment on it. Much appreciated. I have completed #2, and #4 -- those are now committed into SVN. I am working on #1 trying to figure it out. This is my first time, so there is a lot form me to look over and f

Re: [VOTE] Approve the Release of Apache UIMA 2.1.0-incubating

2007-03-05 Thread Daniel Kulp
Adam, On Monday 05 March 2007 13:27, Adam Lally wrote: > Is it sufficient for 3 and 4 to add this information only to our > top-level "uimaj" pom, which is the parent of our other poms? And is > this correct information to add: > > > The Apache Softwar

Implicit SSL

2007-03-05 Thread John Riley
Hi, I read in the documentation that this FTP server supports implicit SSL connections. However, when I dowload the snapshot the configuration files does not look the same as in the configuration. Does it still support implicit SSL? I tried to setup explicit SSL with the test keystore but I didn't

Re: [VOTE] Approve the Release of Apache UIMA 2.1.0-incubating

2007-03-05 Thread Adam Lally
On 2/25/07, Daniel Kulp <[EMAIL PROTECTED]> wrote: A quick look reveals: 1) The jars don't have the incubator disclaimer in them. (this is the critical one) 2) The for jVinci doesn't have "Apache UIMA" in it. 3) The poms don't have a licenses section 4) The tag doesn't have a url to apache.o

Re: [VOTE] Approve the release of Apache Lucene.Net 2.0 build 003 incubating

2007-03-05 Thread William A. Rowe, Jr.
[EMAIL PROTECTED] wrote: > > You cannot call the LICENSE and NOTICE files LICENSE.txt and NOTICE.txt > (I know that it makes sense under Windows). The LICENSE refers > explicitly to a NOTICE file not a NOTICE.txt. Just rename them to > LICENSE and NOTICE as used in the rest of the ASF projects. O

Re: old and new style Apache licenses

2007-03-05 Thread Jean T. Anderson
Marshall Schor wrote: > While going thru some code and changing old-style Apache license headers > to new style ones, a scan > showed that the Apache license, itself, has a section near the bottom, > where it says > > APPENDIX: How to apply the Apache License to your work. > > and then goes on to

old and new style Apache licenses

2007-03-05 Thread Marshall Schor
While going thru some code and changing old-style Apache license headers to new style ones, a scan showed that the Apache license, itself, has a section near the bottom, where it says APPENDIX: How to apply the Apache License to your work. and then goes on to show using the "old style" Apache

Re: [VOTE] Approve the Release of Apache UIMA 2.1.0-incubating

2007-03-05 Thread Marshall Schor
Thanks for your careful review, Jean, much appreciated. We'll fix these issues and retry :-) My understanding is that the Status page needs to be updated by an ASF member - we're working with our Mentors to get this done. If anyone else has comments / issues, please let us know so we can fix

Re: [VOTE] Approve the release of Apache Lucene.Net 2.0 build 003 incubating

2007-03-05 Thread Daniel Kulp
George, On Sunday 04 March 2007 22:38, George Aroush wrote: > Hi Dan, > Many thanks for looking this over. > > For #1 & #2. Can you tell how to go about fixing them? How/where do I > create/get those files? For #1, there is a lot of information at: http://www.apache.org/dev/release-signing.htm

RE: [VOTE] Approve the release of Apache Lucene.Net 2.0 build 003 incubating

2007-03-05 Thread nicko
George, Its great to see Lucene.Net coming along in Apache. It's a tool that I have used for quite some time, in various forms. There are quite a few procedural things to get right when releasing software under the ASF. I know it can feel quite daunting to tick all the boxes (I have had to go thro