You've got to satisfy my curiosity, though. Why would you want to run such a badly out-of-date version in production? I mean, 2.0.0 is just about ready for release, and lagging three full releases behind, with one of them being a major version release, is a long way from where Spark is now.
On Wed, Jul 6, 2016 at 11:12 PM, Niranda Perera <niranda.per...@gmail.com> wrote: > Thanks Reynold > > On Thu, Jul 7, 2016 at 11:40 AM, Reynold Xin <r...@databricks.com> wrote: > >> Yes definitely. >> >> >> On Wed, Jul 6, 2016 at 11:08 PM, Niranda Perera <niranda.per...@gmail.com >> > wrote: >> >>> Thanks Reynold for the prompt response. Do you think we could use a >>> 1.4-branch latest build in a production environment? >>> >>> >>> >>> On Thu, Jul 7, 2016 at 11:33 AM, Reynold Xin <r...@databricks.com> >>> wrote: >>> >>>> I think last time I tried I had some trouble releasing it because the >>>> release scripts no longer work with branch-1.4. You can build from the >>>> branch yourself, but it might be better to upgrade to the later versions. >>>> >>>> On Wed, Jul 6, 2016 at 11:02 PM, Niranda Perera < >>>> niranda.per...@gmail.com> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> May I know if you have halted development in the Spark 1.4 branch? I >>>>> see that there is a release tag for 1.4.2 but it was never released. >>>>> >>>>> Can we expect a 1.4.x bug fixing release anytime soon? >>>>> >>>>> Best >>>>> -- >>>>> Niranda >>>>> @n1r44 <https://twitter.com/N1R44> >>>>> +94-71-554-8430 >>>>> https://pythagoreanscript.wordpress.com/ >>>>> >>>> >>>> >>> >>> >>> -- >>> Niranda >>> @n1r44 <https://twitter.com/N1R44> >>> +94-71-554-8430 >>> https://pythagoreanscript.wordpress.com/ >>> >> >> > > > -- > Niranda > @n1r44 <https://twitter.com/N1R44> > +94-71-554-8430 > https://pythagoreanscript.wordpress.com/ >
