On Mon, Jan 21, 2013 at 7:13 AM, Jukka Zitting wrote:
> Hi,
>
> On Mon, Jan 21, 2013 at 1:39 PM, Michael McCandless
> wrote:
>> I had thought we were supposed to ship the KEYS file next to all release
>> bits.
>
> Yes, my point is just that it's better if it's not expressed as a
> *part* of the
Hi,
On Mon, Jan 21, 2013 at 1:39 PM, Michael McCandless
wrote:
> I had thought we were supposed to ship the KEYS file next to all release bits.
Yes, my point is just that it's better if it's not expressed as a
*part* of the release candidate.
Otherwise there's a risk of implying that one could/
Thanks Jukka.
I had thought we were supposed to ship the KEYS file next to all release bits.
As far as I can tell Lucene and Tika have done this for their past
releases, eg: http://www.eng.lsu.edu/mirrors/apache/tika and
http://apache.mesi.com.ar/lucene/java/4.0.0
But it sounds like this is actu
Thanks Jukka for the FYI...
Cheers,
Chris
On 1/20/13 10:11 PM, "Jukka Zitting" wrote:
>Hi,
>
>On Sun, Jan 20, 2013 at 11:24 PM, Mattmann, Chris A (388J)
> wrote:
>> +1 to that -- Dave feel free to simply copy the one out of dist into the
>> RC dir -- or whomever does the next release feel free
Hi,
On Sun, Jan 20, 2013 at 11:24 PM, Mattmann, Chris A (388J)
wrote:
> +1 to that -- Dave feel free to simply copy the one out of dist into the
> RC dir -- or whomever does the next release feel free to include the KEYS.
There's no particular need for the KEYS file to be included in the RC,
par
