Yes! I can take on RM for 2.2.1. We are still working out what to do with temp files created by Hive and Java that cause the policy issue with CRAN and will report back shortly, hopefully.
________________________________ From: Sean Owen <so...@cloudera.com> Sent: Wednesday, October 25, 2017 4:39:15 AM To: Holden Karau Cc: Felix Cheung; dev@spark.apache.org Subject: Re: Kicking off the process around Spark 2.2.1 It would be reasonably consistent with the timing of other x.y.1 releases, and more release managers sounds useful, yeah. Note also that in theory the code freeze for 2.3.0 starts in about 2 weeks. On Wed, Oct 25, 2017 at 12:29 PM Holden Karau <hol...@pigscanfly.ca<mailto:hol...@pigscanfly.ca>> wrote: Now that Spark 2.1.2 is out it seems like now is a good time to get started on the Spark 2.2.1 release. There are some streaming fixes I’m aware of that would be good to get into a release, is there anything else people are working on for 2.2.1 we should be tracking? To switch it up I’d like to suggest Felix to be the RM for this since there are also likely some R packaging changes to be included in the release. This also gives us a chance to see if my updated release documentation if enough for a new RM to get started from. What do folks think? -- Twitter: https://twitter.com/holdenkarau
