Re: Recovering SparkR on CRAN?

I agree, is there something we can do to ensure CRAN publish goes through consistently and predictably ? If possible, it would be good to continue supporting it. Regards, Mridul On Tue, Dec 22, 2020 at 7:48 PM Felix Cheung wrote: > Ok - it took many years to get it first published, so it was

Re: Recovering SparkR on CRAN?

To clarify, I'm fine with distributing our project by tarball, and would support > Given the current circumstance, I'm thinking of dropping it officially from > the community release scope. +1 (non-binding) michael > On Dec 22, 2020, at 7:47 PM, Felix Cheung wrote: > > Ok - it took many

Re: Recovering SparkR on CRAN?

Ok - it took many years to get it first published, so it was hard to get there. On Tue, Dec 22, 2020 at 5:45 PM Hyukjin Kwon wrote: > Adding @Shivaram Venkataraman and @Felix > Cheung FYI > > 2020년 12월 23일 (수) 오전 9:22, Michael Heuer 님이 작성: > >> Anecdotally, as a project downstream of Spark,

Re: Recovering SparkR on CRAN?

Adding @Shivaram Venkataraman and @Felix Cheung FYI 2020년 12월 23일 (수) 오전 9:22, Michael Heuer 님이 작성: > Anecdotally, as a project downstream of Spark, we've been prevented from > pushing to CRAN because of this > > https://github.com/bigdatagenomics/adam/issues/1851 > > We've given up and marked

Re: Recovering SparkR on CRAN?

Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this https://github.com/bigdatagenomics/adam/issues/1851 We've given up and marked as WontFix. michael > On Dec 22, 2020, at 5:14 PM,

Unsubscribe

Unsubscribe

Re: Recovering SparkR on CRAN?

Given the current circumstance, I'm thinking of dropping it officially from the community release scope. It's because - It turns out that our CRAN check is insufficient to guarantee the availability of SparkR on CRAN. Apache Spark 3.1.0 may not not available on CRAN, too. - In daily CIs, CRAN