CLASSIFICATION: UNCLASSIFIED Can you drop me from the masiling list?
Thanks, Kris T Musshorn CTR CECOM SharePoint Team 443-861-8614 APG Bldg 6002 D5101/108 I am currently teleworking and can be reached at 860 670 9494 -----Original Message----- From: lewis john mcgibbney [mailto:[email protected]] Sent: Thursday, April 23, 2020 4:21 AM To: [email protected] Cc: [email protected] Subject: [Non-DoD Source] Re: [DISCUSS] Release 1.17 ? All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Hi Seb, Go for it. I’ll happily review. Excellent work folks... really excellent work. lewismc On Wed, Apr 22, 2020 at 23:27 <[email protected]> wrote: > > user Digest 23 Apr 2020 06:27:46 -0000 Issue 3055 > > Topics (messages 34517 through 34517) > > [DISCUSS] Release 1.17 ? > 34517 by: Sebastian Nagel > > Administrivia: > > --------------------------------------------------------------------- > To post to the list, e-mail: [email protected] To unsubscribe, > e-mail: [email protected] > For additional commands, e-mail: [email protected] > > ---------------------------------------------------------------------- > > > > > ---------- Forwarded message ---------- > From: Sebastian Nagel <[email protected]> > To: [email protected], [email protected] > Cc: > Bcc: > Date: Thu, 23 Apr 2020 08:27:39 +0200 > Subject: [DISCUSS] Release 1.17 ? > Hi all, > > 30 issues are done now > > Caution-https://issues.apache.org/jira/browse/NUTCH/fixforversion/1234 > 6090 > > including a number of important dependency upgrades: > - Hadoop 3.1 (NUTCH-2777) > - Elasticsearch 7.3.0 REST client (NUTCH-2739) Thanks to Shashanka > Balakuntala Srinivasa for both! > > Dependency upgrades to be included (but still open right now): > - Tika 1.24.1 > - Solr 8.5.1 > > The last release (1.16) was in October, so it's definitely not too > early to release 1.17. As usual, we'll check all remaining issues > whether they should be fixed now or can be done later in 1.18. > > I would be ready to push a release candidate during the next weeks and > have already started to work through the remaining issues. Please, > comment on issues you want to get fixed already in 1.17! > > Thanks, > Sebastian > > -- Caution-http://home.apache.org/~lewismc/ Caution-http://people.apache.org/keys/committer/lewismc CLASSIFICATION: UNCLASSIFIED
