+1 to release!

I verified the signatures, and smoke tested the JAR on a few docs
(should we name it apache-tika-app-NN.jar in the future?  Ie, add
apache- in front), and ran "mvn clean install test" from the src zip.

Mike McCandless

http://blog.mikemccandless.com

On Mon, Sep 26, 2011 at 11:44 AM, Mattmann, Chris A (388J)
<chris.a.mattm...@jpl.nasa.gov> wrote:
> Thanks Jukka.
>
> If that's the case, I'd prefer to simply update CHANGES.txt in the RC zip 
> file,
> in the tag and the branch I'll create (and trunk), and then update the .asc 
> file.
>
> I'll count the existing +1s (and my own +1! :) ) towards the VOTE, and
> let it go until 72 hours and then go from there.
>
> Thanks guys.
>
> Cheers,
> Chris
>
> On Sep 26, 2011, at 8:35 AM, Jukka Zitting wrote:
>
>> Hi,
>>
>>   [x] +1 Release this package as Apache Tika 0.10
>>   [ ] -1 Do not release this package because...
>>
>> On Mon, Sep 26, 2011 at 3:37 PM, Mattmann, Chris A (388J)
>> <chris.a.mattm...@jpl.nasa.gov> wrote:
>>> Would anyone object to me updating the CHANGES.txt file and then respinning
>>> a new RC? I have no problem doing it, and I can use it as an opportunity to
>>> address the other small nits brought up.
>>
>> It should be OK to change the .asc file name and the CHANGES.txt file
>> contents (outside the signed zip file) without cutting a new RC and
>> starting a new vote (neither change has significant legal
>> implications), so either way (recut or update the RC) is fine by me.
>>
>> BR,
>>
>> Jukka Zitting
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>

Reply via email to