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 <https://github.com/bigdatagenomics/adam/issues/1851> We've given up and marked as WontFix. michael > On Dec 22, 2020, at 5:14 PM, Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > > 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 check has been broken frequently due to both our side > and CRAN side issues. Currently, branch-2.4 is broken. > > - It also has a side-effect to cause some delays on the official release > announcement after RC passes because each release manager takes a look at it > if he/she can recover it at that release. > > If we are unable to support SparkR on CRAN in a sustainable way, what about > dropping it official instead? > > Then, it will alleviate burdens on release managers and improves daily CIs' > stability by removing the CRAN check. > > Bests, > Dongjoon. > > > On Mon, Dec 21, 2020 at 7:09 AM Dongjoon Hyun <dongjoon.h...@gmail.com > <mailto:dongjoon.h...@gmail.com>> wrote: > Hi, All. > > The last `SparkR` package of Apache Spark in CRAN is `2.4.6`. > > > https://cran-archive.r-project.org/web/checks/2020/2020-07-10_check_results_SparkR.html > > <https://cran-archive.r-project.org/web/checks/2020/2020-07-10_check_results_SparkR.html> > > The latest three Apache Spark distributions (2.4.7/3.0.0/3.0.1) are not > published to CRAN and the lack of SparkR on CRAN has been considered a > non-release blocker. > > I'm wondering if we are aiming to recover it in Apache Spark 3.1.0. > > Bests, > Dongjoon.
