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> 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> > 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. >> >>
