Personally I'd love for R support to be in 2.4, but I don't consider something "Done" unless tests are running ... Is the proposal: the release manager manually run the R tests when preparing the release, and switch over to fully integrated Jenkins after 2.4.0 is released?
On Wed, Aug 15, 2018 at 2:45 PM Reynold Xin <r...@databricks.com> wrote: > What's the reason we don't want to do the OS updates right now? Is it due > to the unpredictability of potential issues that might happen and end up > delaying 2.4 release? > > > On Wed, Aug 15, 2018 at 2:33 PM Erik Erlandson <eerla...@redhat.com> > wrote: > >> The SparkR support PR is finished, along with integration testing, >> however Shane has requested that the integration testing not be enabled >> until after the 2.4 release because it requires the OS updates he wants to >> test *after* the release. >> >> The integration testing can be run locally, and so the question at hand >> is: would the PMC be willing to consider inclusion of the SparkR for 2.4, >> based on local verification of the testing? The PySpark PR was merged under >> similar circumstances: the testing was verified locally and the PR was >> merged before the testing was enabled for jenkins. >> >> Cheers, >> Erik >> >
