List view
- Due by November 16, 2025•1/1 issues closed
- Due by July 29, 2025•4/4 issues closed
- Due by June 5, 2025•3/3 issues closed
Before submitting future to CRAN: * [x] submit 'parallelly' 1.44.0 (not required) * [x] submit 'globals' 0.18.0 * [x] drop all.equal() for connection (wait for 'parallelly' 1.44.0 to be available on all platforms) * [x] switch to constraints = "connections-16" (wait for 'parallelly' 1.44.0 to be available on all platforms) * [x] 'future.apply' passes all tests with develop versions of 'parallelly', 'globals', and 'future' * [x] 'doFuture' passes all tests with develop versions of 'parallelly', 'globals', and 'future' * [x] 'furrr' passes all tests with develop versions of 'parallelly', 'globals', and 'future'
Due by May 8, 2025•4/4 issues closedPrerequisites: * [x] release updated version of 'parallelly' (MS Windows fixes for `isNodeAlive()`) * [x] release updated version of 'future.tests' (`constant` has been removed) * [x] release updated version of 'doFuture' * [x] CRAN packages 'bigDM' (or after 2025-03-29) * [x] Fix and work around 'promises', which calls evaluator directly * [x] ~~CRAN package 'AICcPermanova' fixed (or after 2025-04-18)~~ * [x] Wait until after ShinyConf 2025 workshops on 2025-04-09 (https://www.shinyconf.com/agenda)
Due by April 10, 2025•26/26 issues closed- Due by July 29, 2024•3/3 issues closed
- Due by March 26, 2024•3/3 issues closed
- Due by December 21, 2023•1/1 issues closed
- Due by July 1, 2023•2/2 issues closed
- Due by March 6, 2023•2/2 issues closed
- Due by January 31, 2023•2/2 issues closed
- Due by December 15, 2022•1/1 issues closed
- Due by November 5, 2022•2/2 issues closed
- Due by September 8, 2022•2/2 issues closed
- Due by May 27, 2022•6/6 issues closed
- Due by April 23, 2022•2/2 issues closed
- Due by February 19, 2022•5/5 issues closed
- Due by October 30, 2021•4/4 issues closed
2021-08-11 Submitted to CRAN. CRAN submission blocker, or at least major friction: There's a bug in R on Windows, cf. R-devel thread 'R for Windows leaves detritus in the temp directory' on 2021-06-15 (https://stat.ethz.ch/pipermail/r-devel/2021-June/080830.html) causing: R CMD check -as-cran on R-devel gives: * checking PDF version of manual ... OK * checking for detritus in the temp directory ... NOTE Found the following files/directories: 'Rscript12e707ecd88b9' 'Rscript171207ecd88c8' * DONE Status: 2 NOTEs
Due by June 18, 2021•10/10 issues closed- Due by December 9, 2020•4/4 issues closed
2020-10-30: Submitted future 1.20.0 to CRAN 2020-10-30: future 1.20.0 failed revdep check of 'photosynthesis' on CRAN. The reason I missed this is that I ran the revdep check of that package using NSLOTS=1 causing it not run with 'multisession' 2020-10-31: Submitted future 1.20.1 to CRAN 2020-11-03: future 1.20.1 accepted on CRAN
Due by October 29, 2020•13/13 issues closedSubmitted future 1.19.0 to CRAN on 2020-09-19. Failed one revdep check on rangeMapper. See Bug #417
Due by September 22, 2020•12/12 issues closed- Due by July 8, 2020•11/11 issues closed
- No due date•4/4 issues closed
Before submitting to CRAN: [x] release future.apply 1.4.0 [x] release doFuture 0.9.0
No due date•4/4 issues closed- No due date•1/1 issues closed
Packages that need to be updated before CRAN submission: * [x] future.BatchJobs * [x] future.batchtools * [x] future.callr * [x] doRNG, cf. https://github.com/renozao/doRNG/issues/12 (notified 2019-10-22) - [x] Alternatively doFuture workaround, cf. https://github.com/HenrikBengtsson/doFuture/issues/38 * [x] kernelboot, cf. https://github.com/twolodzko/kernelboot/issues/6 (notified 2019-10-25; fixed 2019-10-30; CRAN release ETA unknown)
No due date•6/6 issues closed- No due date•6/6 issues closed
- No due date•5/5 issues closed
- No due date•5/5 issues closed
Before release the next version, the following must take place first: 1. future.BatchJobs on CRAN (as of 2019-01-03) 2. future.batchtools on CRAN (as of 2019-01-03) 3. future.callr on CRAN (as of 2019-01-07) 4. doFuture on CRAN (as of 2019-01-07)
No due date•8/8 issues closed- No due date•5/5 issues closed
To do before release: (1) Release new version of [future.apply](https://github.com/HenrikBengtsson/future.apply). This is because we wiped a few internal functions from future and one of future.apply package tests makes use of them (a copy'n'paste mistake)
No due date•5/5 issues closed- No due date•2/2 issues closed
- No due date•6/6 issues closed
- No due date•8/8 issues closed
- No due date•3/3 issues closed
- No due date•1/1 issues closed
- No due date•3/3 issues closed
- No due date•2/2 issues closed
- No due date•6/6 issues closed
- No due date•8/8 issues closed
- No due date•7/7 issues closed
In order to be able to release this one, globals 0.7.0 must appear on CRAN.
No due date•7/7 issues closed- No due date
- No due date•4/4 issues closed
- No due date•1/1 issues closed
- No due date•5/5 issues closed
CRAN release: future 0.7.0
No due date•1/1 issues closed