Thank you, Tim!
Tyler
On May 30, 2017 11:38 AM, "Konstantin Gribov" wrote:
Great work, Tim!
Thanks for managing this release and updating wiki about the process.
On Tue, May 30, 2017 at 9:17 PM Allison, Timothy B.
wrote:
> Please let me know if I botched anything else.
>
> Thank you, again
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mattmann, Chris A (388J) updated TIKA-1804:
---
Hi Everyone,
I will be out of the office 5/29 – 6/6 on Vacation.
During this ti
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029961#comment-16029961
]
Hudson commented on TIKA-1804:
--
SUCCESS: Integrated in Jenkins build Tika-trunk #1280 (See
[h
Great work, Tim!
Thanks for managing this release and updating wiki about the process.
On Tue, May 30, 2017 at 9:17 PM Allison, Timothy B.
wrote:
> Please let me know if I botched anything else.
>
> Thank you, again, Oleg for catching my gaffe on RC1. Thank you Konstantin
> for your help today
Please let me know if I botched anything else.
Thank you, again, Oleg for catching my gaffe on RC1. Thank you Konstantin for
your help today. Thank you Chris, Nick and Tyler for documentation on the
release process!
Cheers,
Tim
From: Tim Allison [mailto:talli...@apache.org]
Sent:
Thank you, again, Konstantin!
-Original Message-
From: Konstantin Gribov [mailto:gros...@gmail.com]
Sent: Tuesday, May 30, 2017 11:59 AM
To: dev@tika.apache.org
Subject: Re: location for javadocs?
IIRC, you should clone `tika-site` svn repo and copy docs there.
On Tue, May 30, 2017 at
> Signature good but there is no trust on key, not a blocker but I think you
> have actually got your key signed by some third parties now, Tim. Have you
> managed to submit your signed key?
Sorry for my daftness...do you mean in the KEYS file in our repo? I just
updated that in trunk.
The Apache Tika project is pleased to announce the release of Apache Tika
1.15. The release contents have been pushed out to the main Apache release site
and to the
Maven Central sync, so the releases should be available as soon as the mirrors
get the syncs.
Apache Tika is a toolkit for detectin
IIRC, you should clone `tika-site` svn repo and copy docs there.
On Tue, May 30, 2017 at 6:45 PM Allison, Timothy B.
wrote:
> Sorry to bother, again, what server do I use to publish the javadocs?
>
>
> mv target/site/apidocs /tika/site/publish/X.Y/api
>
> This doesn't seem to be minotaryIs t
Sorry to bother, again, what server do I use to publish the javadocs?
mv target/site/apidocs /tika/site/publish/X.Y/api
This doesn't seem to be minotaryIs this people.apache.org or another server?
Thank you.
Best,
Tim
Timothy B. Allison, Ph.D.
Principal Artificial In
At least checkout 1.15-rc2 and tag it with 1.15.
I guess, 1.15-rc2 could be deleted afterwards. Or it could be left. I have
small preference for removing it since it gives more noise in `git tag`
output.
On Tue, May 30, 2017 at 4:12 PM Allison, Timothy B.
wrote:
> All,
> In the release proces
All,
In the release process directions, I see this:
5. git clone https://github.com/apache/tika.git X.Y-rcN
6. git tag X.Y && git push --tags
These directions appear to clone trunk and then tag _it_ as 1.15, which can't
be right. Changes might have been made since I cut rc2, and the versi
This VOTE has PASSED with the following tally:
+1
Tim Allison
Konstantin Gribov
Chris Mattmann
David Meikle
Oleg Tikhonov
Many thanks to Oleg Tikhonov for catching problems withRC1. I will finish the
remaining tasksnow.
Best,
Tim
-Original Message-
From: C
13 matches
Mail list logo