We can just say release in December, and code freeze mid Nov? On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen <so...@cloudera.com> wrote:
> Will do, just was waiting for some feedback. I'll give approximate dates > towards the end of the year. It isn't binding or anything. > > > On Mon, Jul 31, 2017, 18:06 Michael Armbrust <mich...@databricks.com> > wrote: > >> +1, should we update https://spark.apache.org/versioning-policy.html ? >> >> On Sun, Jul 30, 2017 at 3:34 PM, Reynold Xin <r...@databricks.com> wrote: >> >>> This is reasonable ... +1 >>> >>> >>> On Sun, Jul 30, 2017 at 2:19 AM, Sean Owen <so...@cloudera.com> wrote: >>> >>>> The project had traditionally posted some guidance about upcoming >>>> releases. The last release cycle was about 6 months. What about penciling >>>> in December 2017 for 2.3.0? http://spark.apache.org >>>> /versioning-policy.html >>>> >>> >>> >>
