|
|
|
|
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
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
Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Ah, I don’t recall actually - maybe it was just missed?
The last message I had, was in June when it was broken by R 4.0.1, which was fixed.
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Let me try in this release - I will have to ask some questions to both of you. I will email you guys offline or private mailing list.
If I happen to be stuck for a difficult reason, I think we can consider dropping it as Dongjoon initially pointed out. Ah, I don’t recall actually - maybe it was just missed?
The last message I had, was in June when it was broken by R 4.0.1, which was fixed.
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
We could just submit the latest release with the fix again. I would not recommend waiting, often time there are some external changes that are not caught, and a fix will need to go through a release vote.
What is the latest release with your fix? 3.0.1? I can put it in but will need to make sure we can get hold of Shivaram.
Let me try in this release - I will have to ask some questions to both of you. I will email you guys offline or private mailing list.
If I happen to be stuck for a difficult reason, I think we can consider dropping it as Dongjoon initially pointed out.
Ah, I don’t recall actually - maybe it was just missed?
The last message I had, was in June when it was broken by R 4.0.1, which was fixed.
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
Nice, yeah, 3.0.1 should have all fixes needed. We could just submit the latest release with the fix again. I would not recommend waiting, often time there are some external changes that are not caught, and a fix will need to go through a release vote.
What is the latest release with your fix? 3.0.1? I can put it in but will need to make sure we can get hold of Shivaram.
Let me try in this release - I will have to ask some questions to both of you. I will email you guys offline or private mailing list.
If I happen to be stuck for a difficult reason, I think we can consider dropping it as Dongjoon initially pointed out.
Ah, I don’t recall actually - maybe it was just missed?
The last message I had, was in June when it was broken by R 4.0.1, which was fixed.
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
|
I just double checked. 3.0.1 is the latest one that has my fix. Nice, yeah, 3.0.1 should have all fixes needed.
We could just submit the latest release with the fix again. I would not recommend waiting, often time there are some external changes that are not caught, and a fix will need to go through a release vote.
What is the latest release with your fix? 3.0.1? I can put it in but will need to make sure we can get hold of Shivaram.
Let me try in this release - I will have to ask some questions to both of you. I will email you guys offline or private mailing list.
If I happen to be stuck for a difficult reason, I think we can consider dropping it as Dongjoon initially pointed out.
Ah, I don’t recall actually - maybe it was just missed?
The last message I had, was in June when it was broken by R 4.0.1, which was fixed.
2020년 12월 23일 (수) 오전 11:21, Mridul Muralidharan < [hidden email]>님이 작성:
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 Ok - it took many years to get it first published, so it was hard to get there.
Anecdotally, as a project downstream of Spark, we've been prevented from pushing to CRAN because of this
We've given up and marked as WontFix.
michael
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.
Hi, All.
The last `SparkR` package of Apache Spark in CRAN is `2.4.6`.
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.
|
|
Locked
