Ok I think we are there, after getting rounds of fixes through in the last few weeks.
I'm going to kick off a separate thread on this to be absolutely clear. ________________________________ From: holden.ka...@gmail.com <holden.ka...@gmail.com> on behalf of Holden Karau <hol...@pigscanfly.ca> Sent: Thursday, November 2, 2017 12:47:13 PM To: Reynold Xin Cc: Felix Cheung; Sean Owen; dev@spark.apache.org Subject: Re: Kicking off the process around Spark 2.2.1 I agree, except in this case we probably want some of the fixes that are going into the maintenance release to be present in the new feature release (like the CRAN issue). On Thu, Nov 2, 2017 at 12:12 PM, Reynold Xin <r...@databricks.com<mailto:r...@databricks.com>> wrote: Why tie a maintenance release to a feature release? They are supposed to be independent and we should be able to make a lot of maintenance releases as needed. On Thu, Nov 2, 2017 at 7:13 PM Sean Owen <so...@cloudera.com<mailto:so...@cloudera.com>> wrote: The feature freeze is "mid November" : http://spark.apache.org/versioning-policy.html Let's say... Nov 15? any body have a better date? Although it'd be nice to get 2.2.1 out sooner than later in all events, and kind of makes sense to get out first, they need not go in order. It just might be distracting to deal with 2 at once. (BTW there was still one outstanding issue from the last release: https://issues.apache.org/jira/browse/SPARK-22401 ) On Thu, Nov 2, 2017 at 6:06 PM Felix Cheung <felixcheun...@hotmail.com<mailto:felixcheun...@hotmail.com>> wrote: I think it will be great to set a feature freeze date for 2.3.0 first, as a minor release. There are a few new stuff that would be good to have and then we will likely need time to stabilize, before cutting RCs. -- Twitter: https://twitter.com/holdenkarau
